Identifying and utilizing the availability of enterprise resources

ABSTRACT

Entities may reference ledgers in order to better understand a historic use and/or status of an account. For example, a user may track historic spending or received payments based on referencing a ledger, or an enterprise may check a balance of an account for a user based on a ledger. However, the utility of ledgers in estimating an amount of funds available for a user&#39;s use is limited. Embodiments of a financial analyzer as described herein may provide entities with estimations of finances that include contributions from one or multiple income sources, including irregular sources. Some embodiments may provide recommendations to customers to meet needs based on a financial estimation.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/743,373, entitled “IDENTIFYING AND UTILIZING THE AVAILABILITY OFENTERPRISE RESOURCES” filed on Jan. 15, 2020. The contents of theaforementioned application are incorporated herein by reference in theirentirety.

BACKGROUND

Transaction records associated with an account may be stored in ledgers.A ledger may record payments and/or deductions of funds to an accountbalance over time. Entities associated with an account may check anaccount balance to understand an amount of funds available in theaccount. Entities may refer to a ledger to understand historictransactions associated with the account.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-J depicts an exemplary user interface according to one or moreembodiments described herein.

FIG. 2 is a block diagram depicting exemplary information exchange in aclient/server environment according to one or more embodiments describedherein.

FIGS. 3A-B is a block diagram depicting exemplary information exchangein a financial analyzer

FIGS. 4A-B are flowcharts depicting financial recommendation techniquesaccording to exemplary embodiments.

FIG. 5 is a block diagram depicting an exemplary computing architecturefor use with techniques described herein.

FIG. 6 is a block diagram depicting an exemplary communicationsarchitecture suitable for use with techniques described herein.

DETAILED DESCRIPTION

Entities may reference ledgers in order to better understand a historicuse and/or status of an account. For example, a user may track historicspending or received payments based on referencing a ledger, or anenterprise may check a balance of an account for a user based on aledger.

Ledgers may include records of transactions associated with a userand/or user account. Records in a ledger may include information such asa transaction amount, as well as other information useful foridentifying the transaction. For example, transaction records mayinclude an amount of funds associated with a transaction, transactiontimestamps, parties associated with a transaction such as a payer and/orrecipient, category of sale, and/or other information. In someembodiments, an enterprise may manage a ledger for a user in associationwith a user account. For example, an enterprise may be a bank, and auser may be a customer of the bank.

However, the utility of ledgers in estimating an amount of fundsavailable for a user's use is limited.

An entity may only be able to understand an availability of funds in anaccount based on a manual analysis of historic records in ledgers, whichcan be time intensive and inconvenient. Understanding transactionpatterns may require traversing through a table of records in a mailedledger, a part purchase list accessed via a website, or an accountledger accessed through an application on a computer. Entities may needto sort historic transactions by various criteria, for example, byinvolved parties, by transaction type, and by time period. The effortand attention to minute detail may prevent a thorough understanding ofhistoric transactions, which may hinder accurate estimations ofavailable funds. For example, a user may forget to account for anupcoming recurring bill in estimating a percentage of funds availablefor casual spending from an account. In another example, a user may nothave time to analyze historic transactions and so may not have anyunderstanding of use of an account.

Furthermore, a ledger may not provide an accurate portrait of currentfunds available in an account. Insight that a customer can gain fromexisting ledgers is limited to already-processed transactions. Delayedexpected transactions, transactions in a transit stage, and/ortransactions completed after an update of a ledger may not appear in theledger as viewable to entities, leaving entities with an incompleteunderstanding of a present status of an account.

Even if an entity is able to analyze historic transactions, they may beunable to reasonably estimate a state of an account based on thehistoric transactions. Historic transactions may be irregular. Forexample, income sources such as gig jobs, hourly jobs, and/or othertask-based jobs may provide a user with irregular income and may notreliably deposit the same amount of funds into an account. A user maynot have access to information about future income and/or expenses. Forexample, a user may not be aware of an upcoming auxiliary bonus from anemployer. Accordingly, manual estimation of upcoming transactions maynot be possible for humans based on historic transactions.

Additionally, or alternatively, entities may not be enabled to respondto an estimation of an account status. For example, a user may guessthat future expenses may outweigh future income. However, the user maynot know how much additional income may be necessary to cover upcomingcosts, or the user may not know how to access necessary additionalincome. A customer may not be aware of potential income sources.Furthermore, a customer may not be aware of products available tomitigate income flow discrepancies. For example, a customer may not beaware that they may qualify for a short-term loan from a bank. In someembodiments, a customer may not be aware of services available topromote account stability and/or growth. For example, a customer may notknow that a bank offers financial counseling.

Accordingly, entities may view tracking finances as a stress-filledchore. In view of the inaccuracies of with manual estimations andhelplessness to properly respond to circumstances at the end, entitiesmay associate negative emotions with tracking finances and/or avoidlooking to their financial future altogether. As a result, entities maybe even less prepared for their financial future. Furthermore, entities'perception of enterprises associated with their transactions may behurt, negatively affecting the business of enterprises.

Given the above weaknesses and concerns, there is a need for an improvedfinancial analyzer. One or more embodiments described herein may enableenterprises to provide at least one solution to one or more of the aboveproblems. For example, embodiments may provide entities with estimationsof finances that include contributions from one or multiple incomesources, including irregular sources. Some embodiments may providerecommendations to customers to meet needs based on a financialestimation. Components described herein will therefore enableenterprises to provide entities with more holistic financial forecasts,to improve efficiency of financial forecasting, and/or to allow entitiesto access recommendations in new ways. Accordingly, in variousembodiments, incorporation of multiple income sources in financialanalyses and/or offerings of recommendations based on analysis ofmultiple income sources may be implemented in a practical application toincrease capabilities and improve adaptability of enterprise systems asa whole.

One or more of the components or techniques described herein may beimplemented via one or more computing devices, resulting in increasedcapability and improved functioning of the computer devices. Specificmanners of automatically estimating financial forecasts, analyzingtrends in customers' finances, and/or dynamically generatingrecommendations may be provided by the components described in variousembodiments herein. In several embodiments, expected behaviors andbehaviors involving the update and management of customer financialestimations and/or recommendations may be performed independently ofsoftware using the request management via familiar, user-friendlyinterface objects.

In various embodiments, components, techniques, or aspects describedherein may be implemented as a set of rules that improvecomputer-related technology by allowing a function not previouslyperformable by a computer that enables an improved technological resultto be achieved. For example, generating an output comprising a productand/or employment recommendation based on a financial estimation madeusing multiple income sources may be an improved technological result.Furthermore, an improved technological result may be presenting and/orproviding the recommendation to a user via a graphical user interface ona user's device.

With general reference to notations and nomenclature used herein, one ormore portions of the detailed description which follows may be presentedin terms of program procedures executed on a computer or network ofcomputers. These procedural descriptions and representations are used bythose skilled in the art to most effectively convey the substances oftheir work to others skilled in the art. A procedure is here, andgenerally, conceived to be a self-consistent sequence of operationsleading to a desired result. These operations are those requiringphysical manipulations of physical quantities. Usually, though notnecessarily, these quantities take the form of electrical, magnetic, oroptical signals capable of being stored, transferred, combined,compared, and otherwise manipulated. It proves convenient at times,principally for reasons of common usage, to refer to these signals asbits, values, elements, symbols, characters, terms, numbers, or thelike. It should be noted, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to those quantities.

Further, these manipulations are often referred to in terms, such asadding or comparing, which are commonly associated with mentaloperations performed by a human operator. However, no such capability ofa human operator is necessary, or desirable in most cases, in any of theoperations described herein that form part of one or more embodiments.Rather, these operations are machine operations. Useful machines forperforming operations of various embodiments include general purposedigital computers as selectively activated or configured by a computerprogram stored within that is written in accordance with the teachingsherein, and/or include apparatus specially constructed for the requiredpurpose. Various embodiments also relate to apparatus or systems forperforming these operations. These apparatuses may be speciallyconstructed for the required purpose or may include a general-purposecomputer. The required structure for a variety of these machines will beapparent from the description given.

Coupling of components will be understood to refer to the presence ofwired connections, wireless connections, network connections, otherconnections, or a combination thereof between the components.

An entity may refer to an individual, a user, or an enterprise. Anenterprise may be an entity or set of entities, such as a business orcompanies, that provides products such as goods or services. Forexample, a bank may be an enterprise. For the sake of simplicity, thedisclosure may refer to enterprises and businesses interchangeably. Itwill be understood that enterprises other than businesses may employ oneor more embodiments described herein. Additionally, the disclosure mayrefer to customers, clients, users, customer accounts, client accounts,user accounts, and/or accounts interchangeably. It will be understoodthat an individual may be a customer and/or a client of an enterprise.Additionally, or alternatively, an individual may be a user of a paymentmethod and/or application associated with an enterprise. A customer,client, and/or user may be associated with an account associated with anenterprise. Embodiments are not limited in this context.

For the sake of simplicity, the disclosure may refer to accounts asbeing financial accounts and/or transactions as being financialtransactions. However, it is understood that embodiments may pertain toother fields. For example, transactions may include non-monetarycurrencies, tokens, or other credits. Accounts may be any record orarrangement associated with a user and a corresponding transaction.Accordingly, a financial analyzer, as described herein, may beunderstood to be an appropriate currency state analyzer, wherein acurrency state corresponds to a status and/or use of a respective bodyof credits.

Reference is now made to the drawings, wherein like reference numeralsare used to refer to like elements throughout. In the followingdescription, for purpose of explanation, numerous specific details areset forth in order to provide a thorough understanding thereof. It maybe evident, however, that the novel embodiments can be practiced withoutthese specific details. In other instances, well known structures anddevices are shown in block diagram form to facilitate a descriptionthereof. The intention is to cover all modification, equivalents, andalternatives within the scope of the claims.

FIG. lA depicts an exemplary user interface 100A according to one ormore embodiments described herein. A business may provide a user withaccess to an account, services, and/or information via a user interface.A user account may include information relating to past transactions ofthe customer. The user interface may include an estimation of financesfor the user. Embodiments are not limited in this context.

A user interface 101 may display information relating to a user account.A user interface may be associated with a website, an application, a webextension, or other program. For simplicity, the present disclosure willrefer to a user interface with respect to an application, butfunctionality of components and/or techniques is not limited to thisexample. A user interface may be accessed via a computer such as alaptop, a desktop, a mobile device such as a mobile phone, or othercomputing device coupled to at least one monitor, input system, and/ormemory. The user interface 101 may include information relating to fundsassociated with the user account. Funds may be physically and/orelectronically maintained. For example, funds may be in a bank account,a digital wallet, a prepaid card, or other financial account. Funds maybe in dollars, points, digital currency, or any other currency. The userinterface 101 may display a balance of funds, such as an availablebalance 102 approved for immediate use and/or a total current balance103 in an account.

In some embodiments, an application may be configured to allowwithdrawals and/or deposits of funds into a fund balance. Depositsand/or withdrawals may be completed according to settings associatedwith an application and/or account. For example, a direct depositsystem's information may be saved with settings for a user account.Alternatively, or additionally, user interface 101 may receiveinstructions to make withdrawals and/or deposits.

In some embodiments, a withdrawals and/or deposits of funds to a user'saccount may be enabled via an application from another user's account.For example, the application of user interface 101 may receive and/ordisplay payment requests such as payment request 104. A payment request104 may be a singular occurrence or a repeating event. Requests and/ordeposits may be managed by the business managing the application, athird party, or a combination thereof.

Requests, such a payment request 104, may include information related tothe request and/or deposit, such as information 105. Information relatedto a request and/or deposit may include an identifier for anotherinvolved account, such as a name and/or account identifier, a valueassociated with the request and/or deposit, a timestamp, and a noteand/or comment provided by at least one user involved in the requestand/or deposit. A user interface 101 may display aspects of information105 in accordance with privacy practices agreed to by at least one user.For example, a name of an account associated with a request may bedisplayed, but not an account number.

A user interface 101 may receive an indication to accept or decline arequest and/or deposit. For example, with respect to payment request104, instructions to decline the request or to send funds to Lucy'saccount can be received at the user interface 101 via options 106. Uponreceiving an indication of a selected option 106, an application mayrespectively decline or complete a payment request 104. In someembodiments, a completed request may be treated as a transaction.

A user interface 101 may display information relating to the flow offunds in and/or out of a financial account. For example, money flow 107may include, with respect to a time frame 108, a measure of incomingfunds and/or outgoing funds. Incoming funds for a time frame 108 may bedisplayed as earned funds 109. Outgoing funds for a time frame 108 maybe displayed as spent funds 110. A time frame 108 may be determined by adefault setting, selected from a plurality of set options, or customized(e.g., daily, weekly, bi-monthly, 60 days, quarterly, bi-annually,annually, etc.). A user interface 101 may display money flow 107 usingtext, numbers, and/or graphical representations.

Embodiments may additionally estimate further incoming and outgoingfunds. Fund estimation may be based at least in part on historic and/orcurrent transaction history, including withdrawal and/or deposit datasuch as resulting from payment requests 104.

Fund estimation may be based on regular and/or irregular transactions.Regular transactions may include regular periodic withdrawals and/ordeposits for substantially the same amount, for example, a monthly rentpayment or a biweekly salary deposit. Irregular transactions may includeaperiodic and/or singular transactions, such as occasional payments torestaurants or occasional payments for task work, such as babysitting.Regular transactions and/or irregular transactions may each beassociated with data about a transaction amount, a transactiontimestamp, and/or contributing and/or involved parties, such as companyidentifiers. In some embodiments, deposits associated with a commonsending party may be determined according to an identifier of the senderto be an income source.

Some embodiments may estimate aspects of incoming and/or outgoingtransactions using one or more models, machine learning, patternfitting, or other method known in the art. Estimated transactions may beassociated with confidence estimations based on historic and/or currenttransactions. Incoming and/or outgoing fund estimations may be based onconfidence estimations for transactions. For example, a singular paymentmay have a low level of confidence indicating it as an event expected torecur, whereas a monthly salary may have a high level of confidence.Accordingly, an embodiment may consider a future salary payment but notan unrelated singular payment in an estimation of incoming funds.

In some embodiments, transactions may be associated with transactioncategories. Estimations may be based on money flow modeled or estimatedfor one or more transaction categories. For example, a “Salary” categorymay be used to estimate a monthly income of $5000 from Employer A, whilea “Miscellaneous” category may be modeled off of irregular payments fromSource P, Source Q, Source R, and Source S and used to estimate anincome of $100 per month, without a specific associated source but basedon the Miscellaneous categorization.

A user interface 101 may display estimated incoming funds in money flow107 as predicted earnings 111. In some embodiments, an application mayconsider information from multiple income sources and display separatepredicted earnings 111 with respect to different income sources orgroups of income sources. A user interface 101 may display estimatedoutgoing funds as predicted spending 112.

Based on one or more of incoming funds, outgoing funds, estimated (e.g.,predicted) incoming funds, and estimated (e.g., predicted) outgoingfunds, embodiments may estimate a net flow of funds associated with afinancial account. A user interface 101 may display an estimate of thenet flow of funds as predicted net flow 113.

Some embodiments may adjust estimation of predicted incoming andoutgoing funds based on adjustment of included transaction sourcesand/or destinations. For example, in user interface 101, options 114 mayenable customization of sources included for these estimations, such asdescribed in greater detail below with respect to FIGS. 1C-1H. Apredicted net flow of funds may be updated or recalculated according tocustomization of parties included in estimations.

A user interface 101 may display data relating to one or moretransactions associated with an associated financial account. Forexample, recent transactions 115 may include one or more current and/orhistoric transactions, such as transaction 116. Transactions may beassociated with timestamps, associated party identifiers such as senderand/or recipient name, transaction categories such as “Restaurants,”transaction amounts, other data useful for identifying a transaction, orany combination thereof. Recent transactions 115 may display a setnumber of transactions 116, such as the twenty with the most recenttimestamps, transactions within a specified time period, such as timeframe 108, or transactions according to another organizational method.Categories of transaction 116 may be the same and/or different ascategories used to estimate incoming and/or outgoing funds as discussedabove.

FIG. 1B depicts an exemplary user interface 100B according to one ormore embodiments described herein. FIG. 1B displays several of the samecomponents as FIG. 1A. For the sake of brevity, such components will notbe described again, but descriptions may be understood according to FIG.1A's description above. However, embodiments are not limited in thiscontext.

In the exemplary user interface 100A, the total of incoming funds (e.g.,earnings 109) and estimated incoming funds (e.g., predicted earnings111) is greater than the total of outgoing funds (e.g., spending 110)and estimated outgoing funds (e.g., predicted spending 112). However, inthe exemplary user interface 100B, the total of outgoing funds (e.g.,spending 110) and estimated outgoing funds (e.g., predicted spending119) is greater than the total of incoming funds (e.g., earnings 109)and estimated incoming funds (e.g., predicted earnings 118).Specifically, as a result of lower estimated incoming funds, predictedearnings 118 is lower in interface 100B than predicted earnings 111. Asa result of higher estimated outgoing funds, predicted earnings 118 ishigher in interface 100B than predicted spending 112. As a result, thepredicted net flow 120 is negative in the example shown in FIG. 1B.

Some embodiments may alert a user when an predicted net flow of funds isnegative. For example, in response to predicted net flow 120 beingnegative, a user interface 101 may display an alert 121.

Additionally, or alternatively, embodiments may offer options to help auser cover a negative estimated fund flow. For example, options for auser to find additional income or find financial assistance may berespectively presented via buttons 122 and 123. Additional income may beadded into calculations by incorporating pre-recognized income sources,such as via a user interface 100C as described with respect to FIG. 1C,and/or additional income sources may be suggested as in a user interface100J as described with respect to FIG. 1J. In some embodiments,financial assistance may be suggested using products and/or servicessuch as in a user interface 100I as described with respect to FIG. 1I.

FIG. 1C depicts an exemplary user interface 100C according to one ormore embodiments described herein. FIG. 1C displays several of the samecomponents as FIGS. 1A-1B. For the sake of brevity, such components willnot be described again, however elements of interfaces described abovemay be referenced and this figure may be understood according to FIGS.1A-1B descriptions above. However, embodiments are not limited in thiscontext.

In the exemplary interface 100C, a user interface 101 may receive aselection of one or more sources of income to inform estimations ofincoming funds. For example, a selection of option 114 as described withrespect to FIG. 1A and FIG. 1B and/or of button 122 as described withrespect to FIG. 1B may direct a user interface 101 to aspects ofinterface 100C. Aspects of an interface 100C may be a pop-up menu, adrop-down menu or a separate page of an application, for example, foundin application settings.

Embodiments may include at least one source of income for use inestimations of incoming funds. For example, predicted earnings detailpage 124 may include one or more income sources 125 to be used inestimations. Sources may be preset, saved by a user, identified byidentifier data associated with historic transactions, or otherwiserecognized by embodiments. Sources may be saved in local or remotememory. One or more sources 125 may be managed by a third party. Someembodiments may integrate an application and/or user interface 101 witha third-party income source, such as via an application programinterface (API). A user interface 101 may enable identification ofadditional income sources. At least one custom income source 125 may bespecified by a user.

Some embodiments may determine estimations of incoming funds based onsources 125. Machine learning and/or at least one model may be used todetermine the reliability of a source 125 and accordingly include orexclude the source 125 from incoming fund estimations. Additionally, oralternatively, a source 125 may be included or excluded from incomingfund estimations based on at least one indication received via a userinterface 101. In some embodiments, machine learning and/or at least onemodel may be used to determine whether a source 125 should be includedor excluded in estimations based on historic indications receivedassociated with that source 125 or with at least one other source 125.For example, a machine learning algorithm may recognize the historicinclusion of a first source in estimations and accordingly include asecond source in estimations based on the similarity between the firstsource and the second source. Embodiments are not limited in thiscontext.

A user interface 101 may receive instructions or indications to includeand/or exclude one or more of the sources 125 in estimations of incomingfunds. For example, selection options 126 may be associated with sources125. In exemplary interface 100C, available sources 125 include “CarService,” “RentYourHome,” “DigitWallet,” “Payroll,” “Bonus Calculator,”and “Custom Source 1.” Based on selection options 126, an embodiment mayinclude “Car Service,” “DigitWallet,” “Payroll,” and “Bonus Calculator”in incoming fund estimations. Selection or deselection of a source 125may override a preset or otherwise predetermined selection of a source125 for inclusion or exclusion from income fund estimations. Estimationsof incoming funds may be updated or recalculated based on selection ordeselection of at least one income source. In some cases, estimates maybe updated or recalculated in real time or near real time according toselections or deselections of sources. Some embodiments may update orrecalculate estimates based on a trigger, such as an exit of a menu asillustrated in interface 100C.

A user interface 101 may present information related to a source 125 ornecessary for use of a source 125 in incoming fund estimations inassociation with the source 125. For example, selection of an option 127may prompt display of details associated with the source 125, such ashistoric and/or transaction information. For example, a user interfacemay display an estimated incoming fund amount in association with anestimated time of the incoming fund. In another example, selection of anoption 127 may redirect a user to an application and/or websiteassociated with an income source 125.

In some embodiments, one or more income sources may require permissionsettings and/or user credentials to be used in fund estimations. Forexample, user login information for a payroll service may be requiredfor a system to interface with the payroll service via an API andthereby retrieve payroll payment information for transactionrecognition. Embodiments may, in some cases, receive permission settinginstructions and/or other information such as login credentials throughan in-application interface, such as that depicted in FIG. 1D.

Many embodiments may determine potential additional income sources(e.g., to include in predicted earnings, or the like) based on one ormore of incoming funds, outgoing funds, estimated incoming funds, orestimated outgoing funds, as described in greater detail below. A userinterface 101 may receive a prompt to display information related to oneor more potential income sources, such as via button 128. For example,embodiments may receive an indication of a selection of button 122 andaccordingly present a user interface 100J as described in greater detailbelow.

FIG. 1D depicts an exemplary user interface 100D according to one ormore embodiments described herein. FIG. 1D displays several of the samecomponents as FIGS. 1A-1C. For the sake of brevity, such components willnot be described again, but descriptions may be understood according toFIGS. 1A-1C's descriptions above. However, embodiments are not limitedin this context.

Interface 100D is part of an exemplary embodiment configured to receiveinformation relating to an income source 125. Sources 125 may requireinformation to log into and/or otherwise connect a user account to athird-party account or service. Embodiments may connect to third-partyaccounts, services, or other platforms via APIs, internet protocols, orother network protocols.

Some embodiments may be prompted to receive information relating to anincome source 125 based on selection of that source 125 for inclusion inan estimation of incoming funds. Additionally, or alternatively,expiration of information and/or a received indication from thethird-party account or service may prompt embodiments to receive new orupdated information.

For example, selection of income source “RentYourHome,” as illustratedin FIG. 1C, may prompt a user interface 101 to receive user credentialsfor RentYourHome. Accordingly, an interface 100D may present a window129. A window 129 may be a pop-up window, a separate page of anapplication, a web page to which the application redirects, or otherentry point suitable for receiving user credentials. Embodiments are notlimited in this context.

A user interface 101 may accordingly receive input of a username andpassword for RentYourHome via fields 130 and 131, respectively. A userinterface 101 may receive an indication that entry of information iscomplete, such as via a submit button 132, and accordingly save theentered information and/or submit the entered information to thethird-party application or service.

Based upon successful entry, submission, and receipt of approval of usercredentials for a third-party system, embodiments may process thethird-party system as a new source 125. Income information from thesource 125 may be retrieved from the third-party system as transactionsto be integrated into existing transaction records, such as thosedisplayed in recent transactions 115 of FIG. 1A, or the data may beprocessed and/or kept independently. Embodiments may retrieve current,recent, and/or historic data.

FIG. 1E depicts a further exemplary user interface 100E according to oneor more embodiments described herein. FIG. 1E displays several of thesame components as FIGS. 1A-1D. For the sake of brevity, such componentswill not be described again, but descriptions may be understoodaccording to FIGS. 1A-1D's descriptions above. However, embodiments arenot limited in this context.

Interface 100E may receive new information and/or updated informationabout a source 125 via window 133. A window 133 may be a pop-up window,a separate page of an application, a web page to which the applicationredirects, or other entry point suitable for receiving information abouta source 125. Embodiments are not limited in this context.

A user interface 101 may present a window 133 to receive new or updateddata about a source 125. For example, a source 125 may be a sourcealready saved with associated data, a newly added source 125, a customsource 125, or a combination thereof.

A user interface 101 may receive an identifier of an income source, suchas an employer number or an employer name, via an employer field 134. Anemployer identifier may be selected from a set of identifiers foremployers associated with platforms set up and/or approved to interfacewith an application. Alternatively, or additionally, an employeridentifier not previously associated with the application may be enteredvia an input device such as a keyboard.

A user interface 101 may receive additional information related to anincome source. In some embodiments, additional information may also be,or alternatively be, related to the user of the user account. Forexample, a user interface 101 may receive an indication of a user's roleand/or job title with respect to an employer identified with an incomesource. In interface 100E, a user interface 101 may receive anindication of a job title for a user employed by BigDataCo in the jobfield 135. A role or job title may be selected from a set of roles orjob titles associated with an employer, such as via a drop-down menu, orbe otherwise entered into window 133.

In some embodiments, information received via a user interface 101 maybe used to access additional information related to a user and/or incomesource 125. For example, receipt of an employer and job title may allowa system to access salary information associated with the role of thejob title with the employer. The salary information may then be used toidentify transaction records as salary payments, as an example.

Additionally, or alternatively, identification of transaction recordsand/or estimation of data flow components may be based on otherinformation received via a user interface 101. While interface 100Eillustrates employer field 134 and job field 135, it will be understoodthat further or different information may be received through a window133. For example, a salary amount, a monthly pay date, time employed, ajob department, or other information may be received.

A system may save information associated with a source 125 via a savebutton 136. Based on saving the information, a system may update orrecalculate processing of transaction data. For example, estimates ofincoming funds may be recalculated or incoming funds may be reclassifiedwith a transaction category specifying an income source 125.

FIG. 1F depicts a further exemplary user interface 100F according to oneor more embodiments described herein. FIG. 1F displays several of thesame components as FIGS. 1A-1E. For the sake of brevity, such componentswill not be described again, but descriptions may be understoodaccording to FIGS. 1A-1E's descriptions above. However, embodiments arenot limited in this context.

In some embodiments, at least one income source may include a bonus,such as an end-of-year bonus. Employees may receive bonuses of pre-knownamounts or bonuses that are determined by at least one of an employer, arole, time employed by the employer, department, co-worker reviews,performance metrics, or other variable terms. If a bonus amount ispredictable, data about the expected payment may be received via a userinterface 101 and saved. For example, bonus data may include theproviding employer, an amount of the estimated bonus, and an estimatedtimestamp of receipt of the bonus.

Alternatively, or additionally, embodiments may include a bonuscalculator. A bonus calculator may estimate at least one bonus amountfor a user based on one or more data sources 137. Data sources 137 mayinclude information related to the user's employment. For example, abonus calculator may base estimations on employer information associatedwith the customer. Some embodiments may include information associatedwith sources 125 in employer information, such as an employeridentifier. Some embodiments may receive and/or retrieve furtherinformation about a user's employment for bonus calculations.

Data sources 137 may additionally, or alternatively, include datamanaged by employers or third-party systems. For example, the source“Glasswindow” may be a website including information about one or morecompanies, including reports from employees about salary and bonusesassociated with job titles, time worked at the company, and co-workerreview data. Data sources 137, like sources 125, may include publiclyaccessible information and/or information only accessible with the useof user credentials or other permission satisfactions.

A bonus calculator may base estimations of a bonus amount based on inputabout the user from at least one co-worker of the user. For example, thebonus calculator may access a co-worker poll as a data source 137. Aco-worker poll may include feedback about the user that have beenfacilitated by the entity of the user application, the employer of anemployee, a third-party system, or a combination thereof. Positivereviews of a user by the user's co-workers may contribute to a higherestimated bonus, for example, or negative reviews may contribute to alower estimated bonus.

A user interface 101 may receive instructions to include and/or excludeone or more data sources 137 in bonus calculations. For example,selection options 139 may be used in at least the same ways as selectionoptions 126. In exemplary interface 100F, the illustrated selection of“Glasswindow” and the deselection of “Co-worker Polls” may directcalculation of an estimated bonus to include data from Glasswindow butnot co-worker polls, for example.

A user interface 101 may receive information related to one or more datasources 137. For example, a bonus calculator interface 138 of a userinterface 101 may include fields such as employer field 134 and jobfield 135 to receive information about a user's employment (not shown).In a further example, a bonus calculator interface 138 may receiveinformation useful for accessing data sources 137 in at least analogousways to a predicted earnings detail page 124. Fields for receivingand/or displaying information relating to a data source 137 may bedisplayed in response to receiving a selection indication of an option140 corresponding to a data source 137.

An estimation may be calculated for a particular time frame. Forexample, a calendar entry 141 may be used to receive an indication of arange of time which an estimation should include, or for which anestimation should account for. In some embodiments, a time frame may bepreset or established as a default.

Embodiments may calculate a bonus based on an indication thatinformation for a calculation has been entered. For example, a userinterface 101 may receive an indication via a calculate button 142.Calculation of a bonus may automatically update an estimation ofincoming funds.

In some embodiments, a preview of an estimated amount may be shown via auser interface 101, such as in preview 143. A preview 143 may be shownbased on a calculation performed as described above.

FIG. 1G depicts a further exemplary user interface 100G according to oneor more embodiments described herein. FIG. 1G displays one or more ofthe same components as FIGS. 1A-1F. For the sake of brevity, suchcomponents will not be described again, but descriptions may beunderstood according to FIGS. 1A-1F's descriptions above. However,embodiments are not limited in this context.

In addition to, or alternatively to, estimations of incoming funds,embodiments may generate estimations of outgoing funds. In the exemplaryinterface 100G, a user interface may receive a selection of one or morecategories or entities associated with outgoing costs to informestimations of outgoing funds. For example, a selection of option 114 asdescribed with respect to FIG. 1A may direct a user interface 101 toaspects of interface 100G. Aspects of an interface 100G may be a pop-upmenu, a drop-down menu or a separate page of an application, forexample, found in application settings.

Embodiments may include at least one spending category for use inestimations of incoming funds. For example, predicted spending detailpage 144 may include one or more spending categories 145 to be used inestimations. Spending categories 145 may be preset, saved by a user,identified by identifier data associated with historic transactions, orotherwise recognized. Spending categories 145 may be saved in local orremote memory. One or more spending categories 145 may be managed by orotherwise associated with a third party. Some embodiments may integratean application and/or user interface 101 with a third-party spendingcategory 145, such as via an API. For example, an application may accessbill data associated with a student loan through a third-party loanprovider by using an API. A user interface 101 may enable identificationof additional spending categories 145. At least one custom spendingcategory 145 may be specified by a user.

Some embodiments may determine estimations of outgoing funds based onspending categories 145. Machine learning and/or at least one model maybe used to determine the reliability of a spending category 145 andaccordingly include or exclude the spending category 145 from outgoingfund estimations. Additionally, or alternatively, a spending category145 may be included or excluded from outgoing fund estimations based onat least one indication received via a user interface 101. In someembodiments, machine learning, pattern fitting, and/or at least onemodel may be used to determine whether a spending category 145 should beincluded or excluded in estimations based on historic indicationsreceived associated with that spending category 145 or with at least oneother spending category 145. For example, a machine learning algorithmmay recognize the historic inclusion of a first spending category inestimations and accordingly include a second spending category inestimations based on the similarity between the first spending categoryand the second spending category. Embodiments are not limited in thiscontext.

A user interface 101 may receive instructions or indications to includeand/or exclude one or more of the spending categories 145 in estimationsof outgoing funds. For example, selection options 146 may be associatedwith spending categories 145. In exemplary interface 100G, availablespending categories include “Rent,” “Healthcare,” “Entertainment,”“Miscellaneous,” “Student Loan 1,” and “Custom Cost 1.” Based onselection options 146, an embodiment may include “Rent,”“Entertainment,” “Miscellaneous,” and “Student Loan 1” in outgoing fundestimations. Selection or deselection of a spending category 145 mayoverride a preset or otherwise predetermined selection of a spendingcategory 145 for inclusion or exclusion from outgoing fund estimations.Estimations of outgoing funds may be updated or recalculated based onselection or deselection of at least one spending category. In somecases, estimates may be updated or recalculated in real time or nearreal time according to selections or deselections of spendingcategories. Some embodiments may update or recalculate estimates basedon a trigger, such as an exit of a menu as illustrated in interface100G.

A user interface 101 may present information related to a spendingcategory 145 in outgoing fund estimations in association with thespending category 145. For example, selection of an option 147 mayprompt display of details associated with the spending category 145,such as historic and/or transaction information. For example, a userinterface may display an estimated outgoing fund amount in associationwith an estimated time of the outgoing fund. In another example,selection of an option 147 may redirect a user to an application and/orwebsite associated with a spending category 145.

In some embodiments, one or more spending categories may requirepermission settings and/or user credentials to be used in fundestimations. For example, user login information for a healthcareprovider may be required for a system to interface with the healthcareprovider via an API and thereby retrieve bill information fortransaction recognition. Embodiments may, in some cases, receivepermission setting instructions and/or other information such as logincredentials through an in-application interface, such as that depictedin user interface 100D.

A system may save information associated with at least one spendingcategory 145 via a save button 148. Based on saving the information, asystem may update or recalculate processing of transaction data. Forexample, estimates of outgoing funds may be recalculated or outgoingfunds may be reclassified with a transaction category specifying aspending category 145.

FIG. 1H depicts an exemplary user interface 100H according to one ormore embodiments described herein. FIG. 1H displays several of the samecomponents as FIGS. 1A-1G. For the sake of brevity, such components willnot be described again, but descriptions may be understood according toFIGS. 1A-1G's descriptions above. However, embodiments are not limitedin this context.

Interface 100H is part of an exemplary embodiment configured to receiveinformation relating to a spending category 145.

Some embodiments may be prompted to receive information relating to aspending category 145 based on selection of that category 145 forinclusion in an estimation of predicted spending. Additionally, oralternatively, expiration of information and/or a received indicationfrom the third-party account or service may prompt embodiments toreceive new or updated information.

For example, selection of spending category “Rent,” as illustrated inuser interface 100G, may prompt a user interface 101 to receive detailsabout a user's rent payments. Accordingly, an interface 100H may presenta window 149. A window 149 may be a pop-up window, a separate page of anapplication, a web page to which the application redirects, or otherentry point suitable for receiving information relating to outgoingfunds. Embodiments are not limited in this context.

A user interface 101 may accordingly receive input of an amount andrecurrence period for Rent via fields 150 and 151, respectively. Fieldsmay receive information via an input device such as a keyboard, viaselection from a set of options presented in a dropdown menu, or otherinput as known in the art. A user interface 101 may receive anindication that entry of information is complete, such as via a savebutton 152, and accordingly save the entered information and/or submitthe entered information to a third-party application or service.

Spending categories 145 may require information to log into and/orotherwise connect a user account to a third-party account or service.Embodiments may connect to third-party accounts, services, or otherplatforms via APIs, internet protocols, or other network protocols. Inthese embodiments, a window 149 may receive user credentials such asdescribed with respect to window 149 of user interface 100H. Embodimentsare not limited in this context.

Based upon successful entry, submission, and receipt of approval of usercredentials for a third-party system, embodiments may process thethird-party system as a new spending category 145. Income informationfrom the spending category 145 may be retrieved from the third-partysystem as transactions to be integrated into existing transactionrecords, such as those displayed in recent transactions 115 of userinterface 100A, or the data may be processed and/or kept independently.Embodiments may retrieve current, recent, and/or historic data.

FIG. 1I depicts an exemplary user interface 1001 according to one ormore embodiments described herein. FIG. 1I displays one or more of thesame components as FIGS. 1A-1H. For the sake of brevity, such componentswill not be described again, but descriptions may be understoodaccording to FIGS. 1A-1H's descriptions above. However, embodiments arenot limited in this context.

Various embodiments may determine one or more recommendations based onestimated incoming and/or outgoing funds. For example, embodiments mayrecommend one or more products or services offered by a business to acustomer. Embodiments may determine a user's eligibility and/orlikelihood to use at least one product and recommend one or moreproducts accordingly. Eligibility may be based on financial history,such as determined using historic transaction data, a credit score, anassociation with at least one other user otherwise eligible, associationwith the business such as a subscription to service, other products orservices used by the customer, other information useful for determiningfinancial security, or any combination thereof. A user's likelihood ofusing a product and/or service may be determined based on at least oneof a historic engagement of the user with a product and/or service, ahistoric engagement of users associated with the user with a productand/or service, a historic engagement of users in a geographic regionassociated with the user with a product and/or service, or a historicengagement of users similar to the user with a product and/or service.

Interface 1001 is part of an exemplary embodiment enabled to presentinformation relating to one or more recommendations.

A user interface 101 may display at least one recommendation relating tofinancial assistance available to and/or recommended for a user. Forexample, financial assistance detail page 153 may include one or morerecommendations 154, 155, and/or 156. Recommendations may relate toproducts and/or services offered by an enterprise. In some embodiments,recommendations may be presented based on a determination ofavailability, user eligibility, and/or user likelihood to engage with aproduct and/or service. In many embodiments, recommendations may bepresented based on a determination that the product and/or serviceoffered may be useful in promoting financial well-being for the user. Invarious embodiments, a user interface 101 display additional informationrelating to a recommendation, such as preview information 157, 158, and159. Preview information may display at least one reason for thepresentation of the recommendation and/or a required action relating tothe recommendation.

For example, recommendation 154 may relate to a short-term loan 1 forwhich the user has been determined to qualify based on credit history,predicted earnings, or the like. For example, short-term loan 1 can bepre-qualified based on verified future income (e.g., via earningscredentials received via window 129, or the like). The short-term loan 1may be for an amount of funds determined to be sufficient to increase apredicted net flow 120 of funds to be a positive value. Previewinformation 157 may be displayed to indicate the user'spre-qualification for the loan. As a further example, recommendation 155may relate to a financial counseling service determined based ongeographical data to be offered at a location within a range of alocation associated with the user. Preview information 158 maycommunicate the geographic proximity as a reason for therecommendation's presentation. In yet a further example, arecommendation 156 may relate to a second short-term loan. As indicatedby preview information 159, further information may be required relatingto the user prior to approval of the loan for the user. Further detailsmay be presented and/or information collected via a user interface 101relating to a recommendation, for example, via an option 160.

FIG. 1J depicts an exemplary user interface 100J according to one ormore embodiments described herein. FIG. 1J displays one or more of thesame components as FIGS. 1A-1I. For the sake of brevity, such componentswill not be described again, but descriptions may be understoodaccording to FIGS. 1A-1I's descriptions above. However, embodiments arenot limited in this context.

Various embodiments may determine one or more additional income sourcesbased on incoming and/or outgoing funds. Additional income sources maybe determined based on a user eligibility and/or likelihood toparticipate in the source.

Eligibility may be based on data about the user relating to historicemployment and/or qualifications. Data relating to historic employmentand/or qualifications of a user may be based on input received from auser and/or information collected in a source. Information relating to auser's eligibility may be received via a user interface. For example, auser interface 101 may receive information relating to a user'semployment history based on questions presented to the user. Someembodiments may collect information to support eligibilitydeterminations from third-party sources according to permissions enabledby the user. For example, a determination of a user's eligibility may bedetermined based on a resume for a user from a job recruitment serviceaccording to access enabled by the user.

A likelihood that a user may engage in an additional income source maybe determined based on at least one of the user's past engagement withan income source, an engagement of a related user with an income source,an engagement of a similar user with an income source, a geographicdistance of the income source from the user, a time requirementassociated with the income source, a user preference setting, or otherconsideration relevant to an employment decision. A user may or may nothave previous association with a presented additional income source.

In various embodiments, an additional income source may be presentedbased on an associated estimated income amount for the income source.For example, the additional income source may be presented based on adetermination that an associated income amount would increase a net flow120 to be positive. Associated income estimations may be based on datarelating to the income source and/or data relating to the user'spotential engagement with the income source. For example, data relatingto the income source may include an hourly pay rate and/or a task-basedpay rate for a position, while data relating to the user's potentialengagement with the income source may include an eligibility for acertain position, an a number of hours the user is available per week,and/or a skill set of the user. In many cases, income sources may bepresented via a user interface 101 based on a determination that theincome source includes an open position relevant to the user. Forexample, income sources without any open positions may not berecommended. A determination of whether an income source has an openposition may be based on an internal database and/or a remote database,which may be managed by the entity associated with the system and/or athird-party entity. For example, a determination of whether an incomesource has an open position may be based on whether the income source asassociated job postings in a recruitment service.

Interface 100J is part of an exemplary embodiment enabled to presentinformation relating to one or more additional income sources.

A user interface 101 may present a user with one or more recommendationsfor supplementary income sources, such as via additional income sourcesdetail page 161. Various embodiments may display information relating toan income source, a position associated with the income source, acommitment expectation relating to the income source, and/or otherinformation relating to the income source. A user interface 101 maydisplay information to provide context for a recommendation of an incomesource.

For example, recommendation 162 may be presented via a user interface101, relating to a position as a driver for a car service. Therecommendation 162 may be presented with associated preview information163, which specifies an expected commitment of five rides given perweek. The expected commitment may be associated with a standard rule setby the income source entity, an availability of the user, and/or anassociated expected income. In some embodiments, the expected commitmentmay be based on an associated expected income to be sufficient toincrease an amount of predicted earnings 118. In another example, arecommendation 164 may be presented for a position of a host with anincome source RentYourHome. The recommendation 164 may be presented withpreview information 165 specifying an expected commitment of three daysper month. In yet another example, a recommendation 166 may be displayedfor an additional income source AnotherJob, which may have an expectedcommitment of ten hours per week, as shown by preview information 167.

Further information relating to an additional income source may bepresented and/or linked to a recommendation. For example, selection ofan option 168 associated with a recommendation may access furtherinformation about an income source and/or role therewith, contactinformation for the income source, a link to a website for the incomesource, and/or other data. In several embodiments, further informationsufficient to enable a customer to take advantage of an additionalincome source may be provided.

FIG. 2 is a block diagram depicting information flow according to one ormore embodiments described herein. Individual components may beimplemented on separate devices, any group of components may beimplemented on the same device, and/or any component may be implementedacross a plurality of devices. Embodiments are not limited in thiscontext.

A client device may be communicatively coupled to a financial analyzer204. A client device may be, for example, a mobile device, a laptop, adesktop computer, or other device. The client device 202 may include aprocessor 206 and/or a memory 208. The memory 208 may include one ormore transitory and/or non-transitory datastores. In some embodiments, amemory 208 may store data related to user data and/or user preferences.

In various embodiments, a memory 208 may include instructions 210.Instructions 210 may be configured to be executed by the processor 206to enable one or more methods described herein.

A client device 202 may include a user interface 212. The user interface212 may be configured to present data based on the operations of theprocessor 206, according to one or more embodiments described herein.For example, a user interface 212 include a user interface 101. Morespecifically, processor 206 in executing instructions 210 may generateuser interface 212 and cause user interface 212 to be presented on adisplay (not shown).

A user interface 212 may be configured to receive input, for example,via a touchscreen, keyboard, number pad, mouse, or other device. Basedon input received via a user interface 212, information may be saved toa memory 208. For example, user preference data and/or data selectionreceived via a user interface 212 may be stored in a memory 208.

In some embodiments, a financial analyzer 204 may be in part or in wholeimplemented on a client device 202. For example, a financial analyzer204 may be implemented via instructions 210. In other embodiments, afinancial analyzer 204 may be located remotely from a client device. Forexample, a financial analyzer 204 may be on a server accessible by atleast one client device 202. In many embodiments, a financial analyzer204 may establish an authenticated communication channel with one ormore aspects of a client device 202, for example, a user interface 212.

A financial analyzer 204 may be configured to calculate amounts of fundsearned and/or spent, such as earned funds 109 and/or spent funds 110, aswell as to estimate incoming and/or outgoing funds, such as predictedearnings 118, predicted spending 119, and predicted net flow 120.

A financial analyzer 204 may be communicatively coupled with at leastone enterprise datastore 214. An enterprise datastore 214 may containinformation relating to one or more user, product, and/or serviceassociated with an enterprise. For example, an enterprise datastore 214may include data relating to an account balance, historic transactionsof a user, or a user setting associated with an account. In anotherexample, an enterprise datastore 214 may include data relating toaccount balances, historic transactions, or user settings of multipleusers, such as a set of users associated with an enterprise.

An enterprise datastore 214 may include data associating one or moreproduct and/or service with a user. For example, an enterprise datastore214 may include a list of products that a particular user is eligiblefor, or an enterprise datastore 214 may include records of requirementsfor product or service eligibility which a user has met. In yet anotherexample, an enterprise datastore 214 may include records relating to auser's historic employment, as enabled by a user setting or otherwiseprovided by the user. At least some data in an enterprise datastore 214may, in some embodiments, be retrieved from a third-party datastore,such as third-party datastore 216.

At least one third-party datastore 216 may be communicatively coupled toa financial analyzer 204. A third-party datastore 216 may includeinformation managed by a third-party entity and not otherwise availableto an enterprise. For example, a third-party datastore 216 may includeincome data or employment data for one or more users associated with theenterprise, one or more job postings, and/or data relating to at leastone product or service offered by a third-party. For example, athird-party datastore 216 may be associated with an income source.

In some embodiments, aspects of an enterprise datastore 214 and/or athird-party datastore 216 may be accessed only after authentication of auser and/or enablement of a privacy setting. For example, a financialanalyzer may access a third-party datastore 216 based on credentialsreceived by a user interface 212 on a client device 202, such as viafields 130 and 131. In many embodiments, a financial analyzer mayestablish an authenticated communication channel with an interfaceassociated with an enterprise, an income source, or another third partybased on received and/or stored credentials. A financial analyzer 204may exchange information with an enterprise datastore 214 and/or athird-party datastore 216 via an interface such as an applicationprogramming interface (API), a web program, or other platform.

In many embodiments, a financial analyzer 204 may process data from atleast one enterprise datastore 214 and/or third-party datastore 216 inorder to generate one or more estimations of income flow for a user. Forexample, a financial analyzer 204 may calculate earned funds 109, spentfunds 110, predicted earnings 111, predicted spending 112, and/orpredicted net flow 113 based on data from an enterprise datastore 214and/or a third-party datastore 216. A financial analyzer 204 maygenerate at least one estimation and/or recommendation based on datafrom an enterprise datastore 214 and/or a third-party datastore 216,such as recommendation 154, 155, 156, 162, 164, and/or 166. In one ormore embodiments, a financial estimation and/or recommendation may bestored to memory associated with the financial analyzer 204, the clientdevice 202, an enterprise datastore 214, and/or a third-party datastore216.

FIG. 3A is a block diagram depicting data structures according to one ormore embodiments described herein. A financial analyzer 204, such asdescribed with respect to FIG. 2, may receive input data 302 and/orgenerate output data 322. Embodiments are not limited in this context.

Input data 302 may comprise at least one message, link, table, datacell, indicator, row, and/or other data structure containing informationuseful for a financial analyzer to operate as described herein. Inputdata 302 may comprise one or more of user data 304, historic income data306, approved income sources 308, custom income sources 310, historicexpense data 312, user performance data 314, available products 316,product qualifications 318, or employment opportunities 320. Input data302 may include data of the same or various types. A financial analyzer204 may receive input data 302 in a single package or multiple packages.For example, a financial analyzer 204 may receive separate input data302 based on the type of data included, based on the source of the dataincluded in the input data 302, and/or based on the component of thefinancial analyzer 204 receiving the input data 302. Input data 302 maycomprise information received from local storage, at least oneenterprise database 214, at least one third-party datastore 216, and/ora combination thereof. For example, input data 302 may comprise all orsome of user data 304 from a database of user data 304. In manyembodiments, user preference settings and/or user selections may be usedto determine which datastore or datastores input data 302 is receivedfrom. In some embodiments, a financial analyzer 204 may receive inputdata 302 based on a query of a database, for example, a database of userdata 304, historic income data 306, approved income sources 308, customincome sources 310, historic expense data 312, user performance data314, available products 316, product qualifications 318, or employmentopportunities 320. Input data 302 may be received via an interface suchas an API, web program, or other platform.

User data 304 may include data associated with at least one user of afinancial analyzer 204. User data 304 may comprise data relating topreference, access and/or security settings, account information for auser, account balance information for a user, saved credentials toaccess information from an enterprise datastore 214 and/or a third-partydatastore 216, credit history data for a user, employment history datafor a user, records of products or services a user has historicallyinteracted with, or other data useful for generating a financialestimation 358 specific to an account for a user. In some embodiments,user data 304 may include comparisons of one or more users to eachother. For example, user data 304 may include a measure of similaritybetween users, indications of groups of similar users, or other metricof comparison of users. Similarity may be based on historic and/orpresent financial wellbeing, credit history, engagement with productsand/or services, and/or other behavioral pattern.

Historic income data 306 may include one or more records relating to theflow of funds into of an account for at least one user. For example,historic income data 306 may comprise a database of ledger records forusers associated with an enterprise. Each record may be associated witha user by a user identifier. In many embodiments, user data 304 maycomprise data corresponding to a user associated with a record ofhistoric income data 306. For example, user data 304 and historic incomedata 306 may comprise data associated with the same user account.Likewise, approved income sources 308 and/or custom income sources 310may comprise data associated with the same user account as data in userdata 304.

In many embodiments, records of historic income data 306 may beassociated with transaction information. Transaction information maycomprise a fund amount, a timestamp, an identifier of at least one partyinvolved in the transaction, and/or an account balance at the time ofthe transaction. In some embodiments, records relating to transactionsfor a user between the user and a common party may be grouped orassociated with each other. For example, historic income data 306 maycomprise transactions representing payments from a particular incomesource, recognized by an identifier of the income source in transactiondata across multiple transactions.

Approved income sources 308 may comprise information relating to one ormore streams of incoming funds. Approved income sources 308 may includeinformation relating to a job and/or position presently and/orhistorically held by at least one user of a financial analyzer 204. Insome embodiments, approved income sources 308 may pertain to jobshistorically held by a single user.

Approved income sources 308 may include information such as anidentifier for the source of incoming funds, an amount of fundshistorically received and/or estimated to be received, a timestamp forat least one historic and/or estimated reception of funds, a metric ofthe reliability and/or confidence of an estimation of continued incomefrom the source, a location of the income source, a schedule of a user'semployment with the income source, and/or other information related toincome sources 308. Income sources 308 may include information relevantto one or more income sources. Income sources may be associated with anentity of the financial analyzer, a third-party entity, or a combinationthereof. In some embodiments, at least one income source of approvedincome sources 308 may be associated with a product offered by anenterprise, such as a loan.

Approved income sources 308 may include a user's association with anincome source, such as a job title, a verification of employment, orother data useful for associating the user with the income source. Invarious embodiments, an income source in approved income sources 308 mayinclude an income priority indicator that the income sources is aprimary, secondary, and/or supplementary income source for a user. Anincome priority indicator may be based on user input, a schedule for theincome source, a comparison of the income source to other income sourcesthe user is employed by, and/or another method of labeling the priorityof the income source for the user. Income sources may contributeregularly or irregularly to a user's income.

In various embodiments, approved income sources 308 may include onlyincome sources which have been verified by a user, a financial analyzer204, and/or an entity associated with the financial analyzer 204. Forexample, an income source may only be included in approved incomesources 308 after a user has provided credentials to verify associationwith the income source. In another example, approved income sources 308may only include an income source after an authentication of incomesource as a legitimate employer by an entity associated with thefinancial analyzer. Approved income sources 308 may comprise datarelating to one or more income source based on an association,agreement, and/or partnership of an entity associated with the financialanalyzer with an entity associated with the one or more income sources.Data included in approved income sources 308 may be preloaded or knownbased on the approval and/or recognition of an income source.

Custom income sources 310 may include data related to at least oneincome source received from a user, such as via a user interface 212.Custom income sources 310 may include one or more components asdescribed with respect to approved income sources 308. Data related tocustom income sources 310 may be related to an income source included inapproved income sources 308 and/or another income source. For example,data in custom income sources 310 may supplement or supersede data foran approved income source. In another example, data in custom incomesources 310 may comprise a record for a new income source. Custom incomesources 310 may be stored in association with a single user account orfor multiple accounts.

Historic expense data 312 may include one or more records relating tothe flow of funds out of an account for at least one user. For example,historic expense data 312 may comprise a database of ledger records forusers associated with an enterprise. Each record may be associated witha user by a user identifier. In many embodiments, records of historicexpense data 312 may be associated with transaction information.Transaction information may comprise a fund amount, a timestamp, anidentifier of at least one party involved in the transaction, and/or anaccount balance at the time of the transaction.

User performance data 314 may include at least one record of a user'sperformance relative to an income source. For example, user performancedata 314 may include at least one of a performance review, a measure ofproductivity in a job, a co-worker poll, or a measure of funds earnedfor an entity. In some embodiments, user performance data 314 mayinclude a record of a user's historic employment with respect to anincome source, for example, a duration of employment in a particularposition. User performance data 314 may be based on an individual useror based on a comparison of metrics for a user to metrics to otheremployees of the entity of the income source.

Available products 316 may include one or more products and/or services.Available products 316 may be offered by an entity associated with thefinancial analyzer, by a third-party entity, or by a combinationthereof. Examples of products may include a loan, a financial grant, aninvestment opportunity, a financial account, a credit card, or otherfinancial product.

Examples of services may include financial counseling, classes relatedto products, or other financial service.

Available products 316 may include qualification requirements. Forexample, requirements may include a credit score above a threshold,approval by an entity associated with the financial analyzer, completionof a class, prior use of another available product and/or service, or acombination thereof.

Product qualifications 318 may include one or more records relating to auser's qualifications for at least one product and/or service. In someembodiments, product qualifications 318 may be associated with aparticular product and/or service. In some embodiments, productqualifications 318 may comprise a list, table, and/or datastore ofgeneralized qualifications. For example, product qualifications 318 mayinclude a user's financial history, credit history, current creditscore, historic engagement with products and/or services, accountbalance, historic account history, recommendations by other entities,eligibility score, income data, or other data useful for determiningproduct and/or service eligibility.

Employment opportunities 320 may comprise one or more availablepositions associated with income sources. In some embodiments,employment opportunities 320 may pertain to income sources which a userhas historically engaged with and/or been employed by. Additionally, oralternatively, employment opportunities 320 may pertain to incomesources which the user has not previously engaged with and/or beenemployed by. For example, a position in employment opportunities 320 maybe associated with an income source of approved income sources 308associated with a similar user.

Employment opportunities 320 may include data associated with at leastone estimated potential income amount, requirements of a position,location of a position, schedule of a position, flexibility of aposition, application data, a link to an application, applicationdeadline data, contact information associated with the income source, aconnection of a user to the position such as association of the userwith an employee of the income source, a link to a website for an incomesource, a position description, and/or other information useful for auser interested in pursuing employment with a position of the employmentopportunities 320. In some embodiments, employment opportunities 320 mayinclude positions based on an estimated income amount for the position,a comparison of position requirements with user data 304 for a user,position and/or schedule comparison of a position to a user'sinformation relative to user data 304 and/or other employment data, suchas employment data from approved income sources 308 and/or custom incomesources 310.

In various embodiments, a financial analyzer may update, generate, addto, or delete information relating to one or more of user data 304,historic income data 306, approved income sources 308, custom incomesources 310, historic expense data 312, user performance data 314,available products 316, product qualifications 318, or employmentopportunities 320. For example, a financial analyzer 204 may receivesetting preferences for a user via a user interface 212. Accordingly,the financial analyzer 204 may update user data 304 with the settingpreferences for the user. In another example, a financial analyzer 204may receive an indication of and/or recognize a user interaction with aproduct. Accordingly, the financial analyzer 204 may update user data304 with a record of the interaction. Embodiments are not limited inthis context.

A financial analyzer 204 may generate output data 322. In manyembodiments, a financial analyzer 204 may generate output data 322 basedon input data 302. Output data 322 may comprise at least one message,link, table, data cell, indicator, row, and/or other data structureincluding one or more of an estimated income 324, employmentrecommendation 326, or product recommendation 328.

An estimated income 324 may include data relating to estimated funds inand/or out of an account. A financial analyzer 204 may generate anestimated income 324 based on records and/or estimates ofincoming/outgoing funds, such as historic income data 306, approvedincome sources 308, custom income sources 310, historic expense data312, and/or indications of user engagement with one or more availableproducts 316 and/or employment opportunities 320. For example, outputdata 322 may be generated with estimated income 324 corresponding toearned funds 109, spent funds 110, predicted earnings 111, predictedspending 112, and/or predicted net flow 113.

An employment recommendation 326 may include one or more positions. Afinancial analyzer 204 may identify one or more positions fromemployment opportunities 320 based on user data 304 and/or income datasuch as included in estimated income 324. In some embodiments, anemployment recommendation 326 may include for each included position anidentifier of the position, a pay rate, a commitment required to earnsufficient funds via the position, contact information for the position,and/or access to an application for the position.

A product recommendation 328 may include an indication of one or moreavailable products 316. A financial analyzer 204 may select one or moreproducts and/or services from available products 316 for inclusion in aproduct recommendation 328 based on an estimated income 324, user data304, available products 316, and/or product qualifications 318.

In various embodiments, output data 322 may include an employmentrecommendation 326 and/or a product recommendation 328 based on adetermination by a financial analyzer 204 that a user's participation ina corresponding position, product, and/or service would be sufficient toincrease an estimated income 324 beyond a threshold. In someembodiments, a financial analyzer 204 may include an employmentrecommendation 326 and/or a product recommendation 328 in output data322 based on the engagement of similar users with a correspondingposition, product, and/or service.

FIG. 3B is a block diagram depicting information flow according to oneor more embodiments described herein. A financial analyzer 204, such asdescribed with respect to FIG. 2, may receive a request 334. In someembodiments, a request 334 may comprise input data 302. In someembodiments, a request 334 may include information to authenticate auser, such as account credentials and/or login information. Based on therequest 334, the financial analyzer 204 may generate a financialestimation 358. The financial analyzer 204 may access data from one ormore communicatively coupled databases, such as at least one enterprisedatastore 214 and/or at least one third-party datastore 216. In someembodiments, data from at least one communicatively coupled database maybe received as input data 302 separate from a request 334. In manyembodiments, settings, preferences, or selections associated with a usermay be used to determine which database or databases input data 302 isreceived from. Individual components of a financial analyzer 204 may beimplemented on separate devices, any group of components may beimplemented on the same device, and/or any component may be implementedacross a plurality of devices. Embodiments are not limited in thiscontext.

A financial analyzer 204 may receive a request 334. A request 334 may bereceived from a device, such as client device 202. In some embodiments,a request 334 may be received via a user interface 212. In someembodiments, a processor 206 may generate a request 334 based oninstructions 210. A request 334 may comprise a log in and/or a requestto access to one or more aspects of functionality of a financialanalyzer 204. For example, a request 334 may be a request based on anindication received by a user interface 212 to estimate, find, and/orpresent at least one additional income source or source of financialassistance available for a user, such as via buttons 122 and 123.

In some embodiments, a new or supplementary request 334 may be generatedbased on indications that parameters for a financial estimation havechanged. For example, if information available to a financial analyzer204 via an enterprise datastore 214 or a third-party datastore has beenupdated, a financial may receive an indication of the update as arequest 334. In another example, a financial analyzer 204 may otherwisedetect a change in an enterprise datastore 214 and/or a third-partydatastore 216 and interpret the update as a request 334. In someembodiments, a request 334 may comprise a list or an update to a list ofsettings and/or sources to include in estimations. For example, arequest 334 may comprise a list of one or more selection options 146selected and/or deselected via a user interface 212, such as describedwith respect to user interface 100G. In a further example, a request 334may include at least one setting for an income source and/or a spendingcategory. For example, a request 334 may include settings for arecurring rent cost, such as those received via fields 150 and 151 inuser interface 100H. In some embodiments, a request 334 may includeadditional user credentials to access data via one or more enterprisedatastores 214 and/or third-party datastores 216. For example, a request334 may include credentials received via fields 130 and 131, asdescribed with respect to user interface 100D. In some embodiments, afinancial analyzer 204 may interpret a request 334 containingcredentials for a datastore as an indication that data from thedatastore should be included in estimations and calculations of thefinancial analyzer 204. In other embodiments, the entry of credentialsfor a source and the selection of the source for inclusion incalculations may be separated.

A financial analyzer 204 may comprise an income determination component336 and/or an income estimation component 342. Either an incomedetermination component 336 or an income estimation component 342, orboth the income determination component 336 and an income estimationcomponent 342, may be used to generate a financial estimation 358. Inmany embodiments, a financial analyzer 204 may process at least onesource of income and/or destination of spending to generate an estimatedincome 324 as part or all of a financial estimation 358. In manyembodiments, financial analyzer 204 may generate the estimated income324 using the income determination component 336 and/or the incomeestimation component 342.

In various embodiments, an income determination component 336 maydetermine income related to one or more income sources. For example, aprimary income analyzation component 338 may determine income related toa primary income source and a secondary income analyzation component 340may determine income related to a secondary income source. One or moreincome sources may be identified as primary, secondary, and/orsupplementary income sources, and one or more income sources may beanalyzed by each of a primary income analyzation component 338, asecondary income analyzation component 340, or other income analyzationcomponent (not illustrated).

An income estimation component 342 may estimate income for a user. Inmany embodiments, income estimations may be for a determined time frame.For example, an income estimation may be for the rest of time in amonth, for a 3-month period, or for a remainder of time in a calendaryear. A time frame may be set by default or by setting.

An income estimation component 342 may estimate income from one or moreincome sources. For example, a primary income estimation component 344may estimate income related to a primary income source and a secondaryincome estimation component 346 may estimate income related to asecondary income source. A primary income estimation component 344and/or secondary income estimation component 346 may estimate income forone or more income sources, for instance, based on an income priorityindicator for each income source. Some embodiments may includeadditional income estimation components (not shown). Income estimationsgenerated by a primary income estimation component 344, a secondaryincome estimation component 346, and/or additional estimation componentsmay be based on input data 302, including one or more of user data 304,historic income data 306, or approved income sources 308, custom incomesources 310.

In some embodiments, a financial analyzer 204 may receive a selection ofan employment opportunity and/or a product, such as included in anemployment recommendation 326 and/or a product recommendation 328.Accordingly, an income estimation component 342 may estimate incomebased on using the employment opportunity and/or product as asupplementary and/or alternative source of income. In some embodiments,an income estimation may be based on the historic contributions of thesame or similar income sources for other or similar users, based on userdata 304. Income estimations generated by a primary income estimationcomponent 344, a secondary income estimation component 346, and/oradditional estimation components may thus be based on input data 302including available products 316 and/or employment opportunities 320.

An income estimation component 342 may include estimated expenses in anincome estimation. For example, an expense estimation component 348 mayestimate expenses for the determined time frame. Historic expense data312 may inform an expense estimation component 348.

In some embodiments, an income estimation component 342 may generate oneor more estimations of expected irregular income sources. For example,an income estimation component 342 may include a bonus calculationcomponent 350. A bonus calculation component 350 may estimate at leastone bonus for a user based on one or more income sources. A bonuscalculation component 350 may estimate a bonus based on past employmentdata and/or past bonuses received by a user, such as may be included inuser data 304. Additionally, or alternatively, a bonus calculationcomponent 350 may use user performance data 314 to estimate a bonus fora user. For example, user performance data 314 including positivereviews of a user by the user's co-workers may contribute to a higherestimated bonus, or negative reviews may contribute to a lower estimatedbonus. In some embodiments, a bonus calculation component 350 mayoperate by logic similar in one or more ways to logic used to processsupplementary income sources. For example, a bonus calculation component350 may implement logic blocks 410, 412, 413, 414, 417, and/or 420 asdescribed below with respect to FIG. 4.

An income estimation component 342 may base inclusion of income sourceson an estimation of the reliability that income will be received fromthe respective income sources. An income reliability estimationcomponent 352 may determine which income sources to include in anestimation and/or weight income amounts based on estimated reliabilitiesof respective income sources. In some embodiments, an income reliabilityestimation component 352 may generate scores and/or other indications ofreliability for at least one income source. For example, an incomesource which has contributed the same amount of funds to an account at aregular interval for a significant period of time may have a highreliability score. In another example, an income source which hasreliably contributed to the incomes of other users similar to the usermay have a high reliability score. In a further example, an incomesource which has irregularly contributed to the income of a user mayhave a low reliability score.

In some embodiments, an estimated income from an income source with alow reliability score may be presented with a lower amount and/or with awarning based on the low reliability score. For example, an incomereliability estimation component may assign a low reliability score toan income source that contributed $100 in a first time period, $0 in asecond time period, and $1000 in a third time period. Accordingly, theincome source may be estimated to contribute an amount greater than $0but less than $1000 in a fourth time period based on the low reliabilityscore.

An income estimation component 342 may generate an estimation of incomeflow based on one or more of a primary income estimation component 344,a secondary income estimation component 346, an expense estimationcomponent 348, a bonus calculation component 350, or an incomereliability estimation component 352. For example, an estimation ofincome flow may be based on a summation of estimated income flow in andout of an account associated with a user. In some embodiments, anestimation of income flow may comprise a flag and/or other indicationthat an estimated summation is positive, negative, and/or below athreshold.

One or more components of an income estimation component 342 may usemachine learning, pattern fitting, and/or at least one model inestimating a component of an estimation of income flow. For example, aprimary income estimation component 344 may estimate income from aprimary source based creating and using a model of historic income datarelating to the primary source. In another example, a bonus calculationcomponent 350 may include a model trained on user data 304 relating toan income source, a position, a user's employment, records of historicbonuses associated with employees of the income source, and/or otherdata. Accordingly, the bonus calculation component 350 may determine anestimated bonus payout based on the model. Similarly, any components ofan income estimation component 342 may include and/or incorporate amodel in generation of an estimation of income flow.

A financial analyzer 204 may comprise an employment recommendationcomponent 354. An employment recommendation component 354 may generateone or more recommendations of employment for a user. In manyembodiments, an employment recommendation component 354 may generate arecommendation of employment based on an estimation of income flow froman income estimation component 342 and/or a recommendation from aproduct recommendation component 356.

An employment recommendation component 354 may generate a recommendationof employment based on one or more aspects of input data 302, forexample, user data 304 and/or employment opportunities 320. In someembodiments, an employment recommendation component 354 may determinethat an estimation of income flow, for example, from an incomeestimation component 342, is below a threshold. For example, theestimation of income flow may be a negative value. Based on theestimation of income flow, the employment recommendation component 354may access one or more employment opportunities 320.

An employment recommendation component 354 may base a recommendation onuser data 304 pertinent to the user request 334. For example, anemployment recommendation component 354 may base a recommendationincluding one or more employment opportunities 320 on a user's credithistory, employment history, schedule, skill set, and/or another factor.

In some embodiments, an employment recommendation component 354 mayaccess employment opportunities 320 based on the interaction of similarusers with those employment opportunities 320, as determined based onuser data 304. For example, an employment recommendation component 354may selectively access and/or filter employment opportunities 320 basedon historic interaction with those employment opportunities 320 by userswith similar estimations of income flow, credit history, employmenthistory, schedule, skill set, and/or another factor.

An employment recommendation component 354 may base a recommendation onmachine learning, pattern fitting, and/or at least one model based onuser data 304. For example, an employment recommendation component 354may use a model including employment opportunities which a user similarto the user of the request 334 may be likely to interact with. Based onthe model, the employment recommendation component 354 may generate arecommendation including an employment opportunity and/or position.

An employment recommendation component 354 may generate a recommendationincluding one or more employment opportunities 320 based on anestimation of income flow. For example, a recommendation may include atleast one employment opportunity of employment opportunities 320 basedon a determination that income gain estimated from the employmentopportunity would increase an estimation of income flow to be above athreshold. A threshold may be based on a default setting, a usersetting, historic estimated income and/or expense data, or anotherfactor. In some embodiments, a recommendation from an employmentrecommendation component 354 may include multiple employmentopportunities 320 that individually and/or together are estimated tocorrespond to an income increase to bring an estimation of an incomeflow above a threshold. The employment recommendation component 354 mayinclude an employment opportunity in a recommendation based on adetermination that the employment opportunity would increase anestimated income flow to be above a threshold in addition to and/or inplace of at least one income source associated with the user.

A recommendation from an employment recommendation component 354 mayinclude contact information for an employment opportunity, a link to awebsite for the employment opportunity, and/or other data to enable acustomer to take advantage of an employment opportunity. Arecommendation may additionally, or alternatively, include informationuseful for determining the estimated value of an employment opportunity.For example, the recommendation may include an estimation of income flowincluding income from the employment opportunity, schedulingrequirements of the income opportunity, reviews of employees associatedwith the employment opportunity, and/or a reliability estimated for theemployment opportunity.

A financial analyzer 204 may include a product recommendation component356. A product recommendation component 356 may generate a one or morerecommendations of a product for a user. In many embodiments, a productrecommendation component 356 may generate a recommendation of a productbased on an estimation of income flow from an income estimationcomponent 342 and/or a recommendation from an employment recommendationcomponent 354.

A product recommendation component 356 may generate a recommendation ofa product based on one or more aspects of input data 302, for example,user data 304, available products 316 and/or product qualifications 318.In some embodiments, a product recommendation component 356 maydetermine that an estimation of income flow, for example, from an incomeestimation component 342, is below a threshold. For example, theestimation of income flow may be a negative value. Based on theestimation of income flow, the product recommendation component 356 mayaccess one or more available products 316.

A product recommendation component 356 may base a recommendation on userdata 304 pertinent to the user request 334. For example, a productrecommendation component 356 may base a recommendation including one ormore available products 316 on a user's financial history, credithistory, historic engagement with available products 316, schedule,estimated eligibility, account balance, and/or another factor. In someembodiments, a product recommendation component 356 may include aproduct in a recommendation based on a determination that the product isassociated with the user request meets. For example, the product may beassociated with one or more product qualifications 318. The productrecommendation component 356 may include the product in a recommendationbased on a determination that the one or more product qualifications 318are met by user data 304 associated with the user of the user request.

In some embodiments, a product recommendation component 356 may accessavailable products 316 based on the interaction of similar users withthose available products 316, as determined based on user data 304. Forexample, a product recommendation component 356 may selectively accessand/or filter available products 316 based on historic interaction withthose available products 316 by users with similar estimations offinancial history, credit history, historic engagement with availableproducts 316, schedule, estimated eligibility, account balance, and/oranother factor.

A product recommendation component 356 may base a recommendation onmachine, pattern fitting, learning and/or at least one model based onuser data 304. For example, a product recommendation component 356 mayuse a model including products which a user similar to the user of therequest 334 may be likely to interact with. Based on the model, theproduct recommendation component 356 may generate a recommendationincluding a particular product.

A product recommendation component 356 may generate a recommendationincluding one or more available products 316 based on an estimation ofincome flow. For example, a recommendation may include at least oneproduct of available products 316 based on a determination that theproduct would result in income gain sufficient to increase an estimationof income flow to be above a threshold. A threshold may be based on adefault setting, a user setting, historic estimated income and/orexpense data, or another factor. In some embodiments, a recommendationfrom an employment recommendation component 354 may include multipleproducts that individually and/or together are estimated to correspondto an income increase to bring an estimation of an income flow above athreshold.

In some embodiments, a product recommendation component 356 may generatea recommendation including one or more products based on one or moreproduct qualifications 318 of another product. For example, a productrecommendation component 356 may determine that a short-term loan wouldbe sufficient to increase an estimation of income flow to be above athreshold, but, based on product qualifications 318 associated with theshort-term loan, the product recommendation component 356 may recognizethat the user needs to take a loan counseling course before beingeligible to take advantage of the short-term loan. Accordingly, theproduct recommendation component 356 may include a loan counselingcourse in a recommendation in addition to or instead of the short-termloan.

A recommendation from a product recommendation component 356 may includecontact information for a product, a link to a website for the product,and/or other data to enable a customer to take advantage of a product. Arecommendation may additionally, or alternatively, include informationuseful for determining the estimated value of a product. For example,the recommendation may include an estimation of income flow includingincome from the product, scheduling requirements of the product, productreviews, and/or an estimated effect of the product for financialwellbeing.

A financial analyzer 204 may generate a financial estimation 358 basedon one or more outputs from an income estimation component 342, anemployment recommendation component 354, and/or a product recommendationcomponent 356. A financial estimation may include one or more aspects ofoutput data 322. In some embodiments, a financial analyzer 204 mayinclude information relating to an estimated income flow, an employmentrecommendation, a product recommendation, or any combination thereof inresponse to an indicator in a received request 334. For example, arequest 334 may indicate a requested analysis of employmentopportunities with respect to an income flow. In another example, arequest 334 may correspond to input received via button 122 as describedwith respect to FIG. 1B. Accordingly, a financial estimation 358 mayinclude an output of an income estimation component 342 and an output ofan employment recommendation component 354 but not a productrecommendation component 356.

In some embodiments, one or more aspects of an income estimationcomponent 342, an employment recommendation component 354, or a productrecommendation component 356 may operate even if a result therefrom isnot to be included in a financial estimation 358 per indicator in arequest 334. Accordingly, a financial analyzer 204 may provide desiredresults based on a holistic analysis of available information. In otherembodiments, one or more aspects of an income estimation component 342an employment recommendation component 354, or a product recommendationcomponent 356 may not operate if a result therefrom is not to beincluded in a financial estimation 358. Accordingly, processingefficiency may be improved.

Criteria for the generation of a financial estimation 358 by a financialanalyzer 204 may be set by default, based on a user setting, selected byan enterprise, determined by information available to a financialanalyzer 204, and/or otherwise customized. For example, a user settingmay limit generation of a recommendation of employment from anemployment recommendation component 354 to include only employmentopportunities 320 and/or available products 316 taken advantage of byusers with similar skill sets. In further examples, a user setting maybroaden recommendations to include employment opportunities 320 and/oravailable products 316 that would require a schedule change of the user,that would require further skill or education, or that have been takenadvantage of by users with dissimilar historic employment.

In many embodiments, one or more aspects of a financial estimation 358may be displayed via a user interface 212, as described with respect toFIG. 2. For example, an employment recommendation of a financialestimation 358 may be displayed as a recommendation 162, 164, and/or 166as described with respect to FIG. 1J. In another example, a productrecommendation of a financial estimation 358 may be displayed as arecommendation 154, 155, and/or 156 as described with respect to FIG.1I. In some embodiments, a financial analyzer 204 may generate a usernotification for display via a user interface 212 based on one or moreaspects of a financial estimation 358. For example, a notification mayinclude indications of potential opportunities to increase an adjustedavailable income and/or indications of offers for financial productsand/or services. The user interface 212 may receive interaction with oneor more aspects of the financial estimation 358, such as interactionwith a recommendation 162, 164, and/or 166. In some embodiments, a userinterface 212 may be redirected and/or progressed based on theinteraction. For example, a user interface 212 may redirect to anapplication for a position based on an interaction with recommendation162.

Next, exemplary logic 400A-B for estimating a net cash flow and/orproviding recommendations based on the estimated net cash flow aredescribed in connection with FIGS. 4A-4B. FIGS. 4A-4B organize the logicblock depicted into various groups of logics (e.g., income determinationlogic 415, income estimation logic 428, product recommendation logic442, income analyzation logic 448, etc.). In some embodiments, theselogic modules may be provided on a client 602 or server 604, as shown inFIG. 6. In some embodiments, these logic modules may be provided on aprocessor 206 and/or in a financial analyzer 204, as shown in FIG. 2,although it is understood that such a configuration is not required. Allthe modules may be implemented in the same device or may be distributedacross any number of devices. Various combinations of modules may beemployed on a given device, or the logic of an individual module may beperformed by different devices.

Processing may begin at block 402, in which a request is received via auser interface. A request may indicate an instruction to generate one ormore financial estimations via a financial analyzer. A request may be,for example, request 334, as described in connection with FIG. 3B. Arequest may be received via a user interface, such as user interface 212described with respect to FIG. 2. A request may be associated with auser and/or user account of a financial analyzer, for example, financialanalyzer 204.

From block 402, processing may proceed to block 404. At block 404, logicmay receive an indication of a primary income stream. In someembodiments, logic may receive an indication of a primary income streamas an information element received in input data 302, as described withrespect to FIG. 3A. An indication of a primary income stream maycorrespond to a repeated contribution of income to a user account by acommon source. For example, a primary income stream may correspond towages earned from an employer, to payments made by an entity to the useraccount, or other source. In some embodiments, a request of block 402may comprise an indication of a primary income stream. Accordingly,logic of blocks 402 and 404 may be performed concurrently or in the samestep or steps.

In some embodiments, logic may identify an indication of a primaryincome stream based on a setting, user input, and/or historic dataassociated with the user and/or user account of block 402. For example,logic may identify repeated contributions above a threshold fund amountby a common source as an income source. A primary income stream may beidentified from one or more income sources based on relativeconsistencies and/or values of contributions from the respective incomesources. For example, logic may determine an indication of a primaryincome stream based on identification of a source of regularcontributions with larger magnitudes than other sources of regularcontributions.

From block 404, logic may hand off processing to block 406, block 407,and/or 408.

At block 406, logic may identify a source of a primary income stream. Asource of a primary income stream may comprise a source identifierindicating a primary income stream. A source may be identified based ona setting, user input, and/or based on historic transactions in anaccount for the user. For example, transactions determined at block 404and/or block 407 to be associated with a primary income source mayinclude a common source identifier. In some embodiments, logic mayreceive one or more aspects of a source of a primary income stream as aninformation element received in input data 302, as described withrespect to FIG. 3A. For example, a source of a primary income stream maybe received as an aspect of approved income sources 308 and/or customincome sources 310. In some embodiments, multiple entities may begrouped and identified as a common source at block 406. For example,entities may belong to a common category and/or have a common tag, forexample, a tag indicating income from a particular type of source, suchas payments for salaried work and/or gig work. Examples of salaried workmay include payments of regular amounts made based on defined paymentcycles. Examples of income sources associated with gig work may includea ride hailing service, a rental service, a media streaming service, acontent distribution service, or a social media service.

In some embodiments, logic at block 406 may identify additional dataassociated with a source identifier indicating a primary income stream.Additional data may comprise information useful for determining paymentsassociated with a primary income stream. Additional data may beidentified based on information received from an enterprise datastore214 and/or a third-party datastore 216, as described with respect toFIG. 2. For example, additional data may comprise reports of an incomesource's historic wages for at least one position, for example, from ajob information reporting database. In some embodiments, additionalinformation may comprise an indication of a reliability, consistency,and/or a payment cycle associated with an income source. In someembodiments, logic may receive additional data as an information elementreceived in input data 302, as described with respect to FIG. 3A. Forexample, additional data may be received in historic income data 306,approved income sources 308, and/or custom income sources 310.

At block 407, logic may identify actions associated with a primaryincome stream. Actions may be identified in data and correspond toreceived and/or estimated incoming funds. For example, an action mayinclude a transaction record, a schedule entry of an employment shift,data corresponding to worked overtime, or another action relating to aprimary income stream. In some embodiments, logic may receive anindication of at least one action as an information element received ininput data 302, as described with respect to FIG. 3A. For example,actions may be received as historic income data 306. Actions may becompleted, incomplete, or a combination thereof. For example, acompleted action may include a received wage. In another example, anincomplete action may include an estimated wage that has not yet beenreceived. Some embodiments may include logic to identify completedactions in a payment cycle, completed actions related to the paymentcycle in a specified time period, or a combination thereof. Logic atblock 407 may identify actions over multiple iterations of a specifiedtime period and calculate an average number of completed actions in aspecified time period.

Logic at block 408 may identify user data associated with a primaryincome stream. For example, user data identified at block 408 maycomprise a position held by a user in association with an income source,a pay rate, a performance review, an indication of a user's employmenthistory in association with an income source, or any combinationthereof. In some embodiments, logic may receive an indication of userdata as an information element received in input data 302, as describedwith respect to FIG. 3A. For example, data may be received as user data304 and/or user performance data 314.

In many embodiments, logic may proceed from block 402 to block 410.Logic may hand off processing to block 410 alternative to or in additionto block 404. Processing may take place either at block 404 or block 410first, or processing may take place at blocks 404 and 410 concurrently.At block 410, logic may receive an indication of at least onesupplemental income stream. In some embodiments, a request of block 402may comprise an indication of a supplemental income stream. Accordingly,logic of blocks 402 and 410 may be performed concurrently or in the samestep or steps.

An indication of a supplemental income stream may correspond to arepeated contribution of income to a user account by a common sourcethat is supplemental to a primary income stream. For example, asupplemental income stream may correspond to wages earned from anemployer, to payments made by an entity to the user account, or othersource. In many embodiments, a supplemental income stream may includeincome contributions that are regularly less in value than and/or lessreliable than contributions of a primary income stream. A supplementalincome stream may be identified based on a category of transaction, forexample, of gig work. Examples of income sources associated with gigwork may include a ride hailing service, a rental service, a mediastreaming service, a content distribution service, or a social mediaservice.

In some embodiments, a supplemental income stream may comprise anirregular payment. In some embodiments, the supplemental income streammay be associated with a primary income stream. For example, asupplemental income stream may comprise an auxiliary bonus associatedwith a primary income source, such as a primary income bonus.

In other embodiments, logic may identify an indication of a supplementalincome stream based on a setting, user input, and/or historic dataassociated with the user and/or user account of block 402. For example,logic may identify repeated contributions above and/or below a thresholdfund amount by a common source as an income source. A supplementalincome stream may be identified from one or more income sources based onrelative consistencies and/or values of contributions from therespective income sources. For example, logic may determine anindication of a supplemental income stream based on identification of asource of regular contributions with smaller magnitudes than a primaryincome source but larger magnitudes than other sources of regularcontributions. In some embodiments, logic may receive an indication of asupplemental income stream as an information element received in inputdata 302, as described with respect to FIG. 3A. For example, anindication of a supplemental income stream may be received in approvedincome sources 308 and/or custom income sources 310.

From block 410, logic may hand off processing to block 412, block 413,and/or block 414.

At block 412, logic may identify a source of a supplemental incomestream. A source of a supplemental income stream may comprise a sourceidentifier indicating a primary income stream. A source may beidentified based on a setting, user input, and/or based on historictransactions in an account for the user. For example, transactionsdetermined at block 410 and/or block 413 to be associated with asupplemental income source may include a common source identifier. Insome embodiments, logic may receive a source of a supplemental incomestream as an information element received in input data 302, asdescribed with respect to FIG. 3A. For example, an indication of asupplemental income stream may be received in approved income sources308 and/or custom income sources 310. In some embodiments, multipleentities may be grouped and identified as a common source at block 412.For example, entities may belong to a common category and/or have acommon tag, for example, a tag indicating income from a particular typeof source, such as payments for gig work.

In some embodiments, logic at block 412 may identify additional dataassociated with a source identifier indicating a supplemental incomestream. Additional data may comprise information useful for determiningpayments associated with a supplemental income stream. Additional datamay be identified based on information received from an enterprisedatastore 214 and/or a third-party datastore 216, as described withrespect to FIG. 2. For example, additional data may comprise reports ofan income source's historic wages for at least one position, forexample, from a job information reporting database. In some embodiments,additional information may comprise an indication of a reliability,consistency, and/or a payment cycle associated with an income source. Ifa supplemental income stream comprises an auxiliary bonus from an incomesource, additional data may comprise related auxiliary payout metrics.In some embodiments, logic may receive additional data relating to asupplemental income stream as an information element received in inputdata 302, as described with respect to FIG. 3A. For example, anindication of a supplemental income stream may be received in historicincome data 306, approved income sources 308, and/or custom incomesources 310.

At block 413, logic may identify actions associated with a supplementalincome stream. Actions may be identified in data and correspond toreceived and/or estimated incoming funds. For example, an action mayinclude a transaction record, a schedule entry of an employment shift,data corresponding to worked overtime, or another action relating to asupplemental income stream. In some embodiments, logic may receive anindication of at least one action as an information element received ininput data 302, as described with respect to FIG. 3A. For example, anindication of at least one action may be received in approved historicincome data 306. Actions may be completed, incomplete, or a combinationthereof. For example, a completed action may include a received wage. Inanother example, an incomplete action may include an estimated wage thathas not yet been received. Some embodiments may include logic toidentify completed actions in a payment cycle, completed actions relatedto the payment cycle in a specified time period, or a combinationthereof. Logic at block 413 may identify actions over multipleiterations of a specified time period and calculate an average number ofcompleted actions in a specified time period.

Logic at block 414 may identify user data associated with a supplementalincome stream. For example, user data identified at block 408 maycomprise a position held by a user in association with an income source,a pay rate, a performance review, an indication of a user's employmenthistory in association with an income source, or any combinationthereof. In some embodiments, logic may receive user data as aninformation element received in input data 302, as described withrespect to FIG. 3A. For example, user data associated with asupplemental income stream may be received in user data 304 and/or userperformance data 314.

Together, logic of blocks 404, 406, 407, 410, 412, and 413 make upincome determination logic 415. It is understood that while aspects ofincome determination logic 415 are illustrated singularly for the sakeof simplicity, logic of any block may be performed in any number ofiterations. In some embodiments, logic may receive indications ofmultiple primary and/or supplemental income streams, thereby performingthe steps of blocks 404 and/or 410 respectively multiple times. Forexample, logic may receive an indication of a secondary supplementalincome stream at block 410 and accordingly proceed to logic of blocks412 and 413. Subsequently or simultaneously, logic may receive anindication of a third, fourth, or further supplemental income stream atblock 410. Accordingly, logic may perform steps of blocks 412 and 413for each received income stream indication. Logic may perform stems inseries or in parallel. One or more aspects of income determination logic415 may be performed by a processor 206 and/or financial analyzer 204,as described with respect to FIG. 2.

From block 406, 407, and/or block 408, processing may progress to block416. At block 416, logic may determine a probability of a primaryincome. The probability of the primary income may comprise a likelihoodthat a payment will be completed by a primary income source. Logic maydetermine a probability based on a source of a primary income stream asdetermined in block 406, actions associated with the primary incomestream as determined in block 407, user data associated with the primaryincome stream, as determined in block 408, or any combination thereof.For example, logic may calculate a probability of a future payment froma primary income source based on third-party reports relating topayments by the primary income source, historic actions associated withthe primary income source, whether the actions are completed and/oraverage completed actions, an amount associated with historictransactions from the primary income source, a calculated reliabilityand/or consistency of historic payments, or any combination thereof.

Logic may determine a probability of primary income in association witha specified time period. A specified time period may be determined bysetting, received user input, historic transaction data, and/or otherdata associated with the primary income source. For example, logic mayidentify a pattern in timestamps of historic transaction data associatedwith the primary income source, wherein the pattern indicates a paymentcycle. Accordingly, logic may determine a specified time period based onthe identified payment cycle.

If logic, via block 404, received indications of multiple primary incomestreams, then logic of block 416 may be performed separately for eachprimary income stream or once for all identified primary income streams.

From block 416, processing may progress to block 418. At block 418,logic may estimate and/or predict a quantity of primary income. Logicmay predict a quantity of primary income based on a source of and/or atleast one action associated with a primary income stream, as determinedby income determination logic 415. A prediction of a quantity of primaryincome may be based on a probability associated with receiving at leastone payment from a primary income source, as determined in block 416. Iflogic, via block 404, received indications of multiple primary incomestreams, then logic of block 418 may be performed separately for eachprimary income stream or once for all identified primary income streams.For example, logic of block 418 may predict a quantity of primary incomebased on multiple primary income sources. A prediction of a quantity ofprimary income may include an estimate of incoming funds from at leastone primary income source over a specified time period, wherein the timeperiod is determined based on a default setting, a user setting, and/orother measurement setting. For example, a time period may be specifiedbased on a recurrent payment cycle.

From block 412, 413, and/or 414, processing may progress to block 417.At block 417, logic may determine a probability of a supplementaryincome. The probability of the supplementary income may comprise alikelihood that a payment will be completed by a supplementary incomesource. Logic may determine a probability based on a source of asupplementary income stream as determined in block 412, actionsassociated with the supplementary income stream as determined in block413, user data associated with the supplementary income stream, asdetermined in block 414, or any combination thereof. For example, logicmay calculate a probability of a future payment from a supplementaryincome source based on third-party reports relating to payments by thesupplementary income source, historic actions associated with thesupplementary income source, whether the actions were completed and/oraverage completed actions, an amount associated with historictransactions from the supplementary income source, a calculatedsupplementary and/or consistency of historic payments, reviews of theuser's performance associated with the supplementary income source, orany combination thereof. For example, if a secondary income streamcorresponds to an auxiliary bonus, logic at block 417 may determine aprobability of a user receiving an amount as a bonus based on historicbonuses received from the corresponding income source, time spent in aposition associated with the income source, performance reviews for theuser associated with the income source, and reports of bonuses receivedby similar employees of the income source.

Logic may determine a probability of supplementary income in associationwith a specified time period. A specified time period may be determinedby setting, received user input, historic transaction data, and/or otherdata associated with an income source. For example, logic may identify apattern in timestamps of historic transaction data associated with anincome source, wherein the pattern indicates a payment cycle.Accordingly, logic may determine a specified time period based on theidentified payment cycle.

If logic, via block 410, received indications of multiple supplementaryincome streams, then logic of block 417 may be performed separately foreach supplementary income stream or once for all identifiedsupplementary income streams.

Processing may progress from block 417 to block 420. At block 420, logicmay estimate and/or predict a quantity of supplemental income. Logic maypredict a quantity of supplemental income based on a source of and/or atleast one action associated with a supplemental income stream, asdetermined by income determination logic 415. A prediction of a quantityof supplemental income may be based on a probability associated with asupplemental income, as determined in block 417. If logic, via block410, received indications of multiple supplemental income streams, thenlogic of block 420 may be performed separately for each supplementalincome stream or once for all identified supplemental income streams.For example, logic of block 420 may predict a quantity of supplementalincome based on multiple supplemental income sources. A prediction of aquantity of supplemental income may include an estimate of incomingfunds from at least one supplemental income source over a time period,wherein the time period is determined based on a default setting, a usersetting, and/or other measurement setting. In many embodiments, the timeperiod associated with the prediction of a quantity of supplementalincome may be the same time period associated with a prediction of aquantity of primary income.

At block 422, logic may identify historic expense data. Historic expensedata may be identified as historic transactions resulting in a deductionfrom funds in an account. In some embodiments, historic expense data maybe identified in association with one or more entities associated withexpenditures.

Based on historic expense data identified at block 422, logic maypredict a quantity of expenses at block 424. Logic may predict aquantity of expenses based on a value and/or recurrence of one or morehistoric expenses. In some embodiments, reliability of expenses may bebased on association of expenditures with one or more entities, and theprediction of the quantity of expenses may be based on the reliability.Logic may use machine learning, one or more models, pattern fitting,and/or other measure to estimate a quantity of expenses for theprediction. A prediction of a quantity of expenses may include anestimate of expenses for a particular time period. The time period ofthe prediction may be based on a default setting, a user preference,and/or another setting. In many embodiments, a time period of theprediction may be the same as a time period associated with a predictionof a quantity of primary income, of supplemental income, or both.

From block 424, processing may be handed off to block 426. At block 426,logic may determine an adjusted available income. An adjusted availableincome may be based on one or more of determinations of logic at blocks418, 420, or 424. For example, an adjusted available income may includea summation of predicted quantities of primary income, supplementalincome, and/or expenses. In some embodiments, data may be included in anadjusted available income based on a default setting, a user setting, orother selection. For example, a user setting may specify that anadjusted available income should be calculated based on a primary incomeprediction and an expense prediction, but not based on a supplementalincome prediction. In another example, a user interface 212 as describedwith respect to FIG. 2 may receive instructions that cause an adjustedavailable income to be calculated based on a supplemental incomeprediction and an expense prediction, but not based on a primary incomeprediction.

Together, logic of blocks 418, 420, 422, 424, and 426 may make up incomeestimation logic 428. One or more aspects of income estimation logic 428may be performed by a processor 206 and/or financial analyzer 204, asdescribed with respect to FIG. 2.

In some embodiments, processing may progress from block 426 to block430. At block 430, logic may provide an adjusted available income fordisplay, for example, via a user interface 212 as described with respectto FIG. 2. As described with respect to FIG. 1A, an adjusted availableincome may be displayed as predicted net flow 113.

Processing may be handed off from block 426 to block 432. As describedin exemplary logic 400B, logic may determine at block 432 whether anadjusted available income is less than a threshold. A threshold may bedetermined by a setting such as a default setting or a user setting. Forexample, a threshold may be $0, in which an adjusted available incomeless than the threshold may indicate an estimation that estimatedexpenses for a user are greater than estimated income. In anotherexample, a threshold may be a positive value, in which an adjustedavailable income less than the threshold may indicate that an estimatednet gain of funds may not meet a user's savings goal.

If logic at block 432 determines that an adjusted available income isnot less than the threshold, processing may end. Otherwise, processingmay progress to block 434. At block 434, logic may determine an amountneeded to meet the threshold based on a comparison of the adjustedavailable income to the threshold. For example, an amount needed to meetthe threshold may be a difference between an adjusted available incomeand the threshold.

From block 434, processing may proceed to block 436. At block 436, logicmay identify users with similar data. Logic may use user data 304 toidentify users with similar data, as described with respect to FIG. 3A.For example, logic may compare data associated with a user to dataassociated with other users. In another example, logic may identifysimilar users and/or users with a similar financial history to a userbased on a model. Logic may use financial history, employment records,skill sets, defined categories, or other data to identify similar users.

Some embodiments may skip the processing of block 438 or determine thatall users in a category and/or associated with a financial analyzer maybe similar. In these embodiments, processing may proceed directly fromblock 434 to block 438 and/or block 446. Otherwise, processing may behanded off from block 436 to block 438 and/or block 446.

At block 438, logic may identify products. Products may include at leastone good and/or service useful for achieving a financial end. Forexample, a good may be a loan, a mortgage, a financial grant, aninvestment account, and/or another product offered by an entity. Aservice may be, for example, a financial counseling class. Logic mayidentify products based on an amount to meet a threshold, as describedwith respect to block 434, based on the engagement of similar users withproducts, wherein the similar users are those determined in block 436,based on a requirement of another product or an income source, and/orother data as described herein.

Processing may be passed from block 438 to block 440. At block 440,logic may determine whether a user is eligible for the productsidentified in block 438. The determination may be based on productqualifications 318 associated with the products, user data 304, anaccount history, other data described herein, or any combinationthereof. Logic may determine whether the user is eligible for theproducts based on a comparison of data associated with the user to dataassociated with the product and/or requirements for the product.

If logic determines that the user is eligible for the products,processing may progress to block 444. Otherwise, processing may returnto block 434 or block 436. Next, logic may re-enter logic of block 438to select alternative products. Additionally, or alternatively, logicmay progress to block 446.

Logic of blocks 438 and 440 may make up product recommendation logic442. A financial analyzer 204 and/or a processor 206, such as describedin connection with FIG. 2, may perform product recommendation logic 442.

At block 444, logic may calculate a theoretical adjusted income. Thetheoretical adjusted income may be a combination of an adjustedavailable income with the effects of the products for which the user isdetermined to be eligible in block 440.

At block 446, logic may identify at least one additional income source.The at least one additional income source may be selected, for example,from employment opportunities 320 based on information such as theamount determined in block 434 to be needed to meet a threshold, userexperience and availability as found in user data 304, and/orrequirements of the at least one additional income source. Logic ofblock 446 may make up income analyzation logic 448, which may beimplemented by a processor 206 and/or a financial analyzer 204, asdescribed in connection with FIG. 2.

In some embodiments, logic of block 446 may be implemented with a checkof user eligibility and/or availability, as illustrated with respect toproduct recommendation logic 442 in block 440. In the case that a useris ineligible and/or unable to take advantage of the additional incomesource identified in block 446, logic may return to block 436 or block434 as described above. Otherwise, processing may progress to block 444.Alternatively, logic may be implemented in a single step, where at leastone additional income source is identified in block 446 based on usereligibility and/or availability. For example, an income source may onlybe identified in block 446 based on a comparison of the user'squalifications with the income source's requirements. A determinationthat the income source's requirements are met by the user'squalifications may indicate that the user is a good candidate for theincome source, and the income source may be accordingly identified inblock 446. Similarly, blocks 438 and 440 of product recommendation logic442 may be implemented in a common step.

Logic may progress from income analyzation logic 448 to block 444. Inthis case, a calculation of a theoretical adjusted income at block 444may include the effects of the additional income source identified inblock 446 in addition to or alternative to the effects of the productsidentified in block 438. For example, logic at block 444 may calculate atheoretical adjusted income as a combination of an adjusted availableincome with estimated income associated with an income source identifiedat block 446.

From block 444, logic may proceed to block 450. At block 450, logic maydetermine whether a theoretical adjusted income is less than athreshold. In many embodiments, the threshold of block 450 may be thesame threshold of block 432. If the theoretical adjusted income isdetermined to be less than the threshold, logic may implement steps toidentify at least one further product and/or income source to supplementthe adjusted available income. Specifically, logic may enter stepsdescribed with respect to 434.

In some embodiments, logic may return to block 434 while maintaining theeffect of the at least one product and/or income source analyzed atblock 450. In other words, the theoretical adjusted income of block 450may be treated as an adjusted available income of block 432. The effectsof another product and/or income source subsequently identified byrespective logic at block 438 and/or 446 may be added to the newlyassumed adjusted available income.

In some embodiments, logic may return to block 434 after disregardingthe effect of the at least one product and/or income source analyzed atblock 450. Accordingly, logic at block 438 and/or block 446 may identifyat least one product and/or income source as a replacement for thatpreviously determined at block 450 to be insufficient to raise thetheoretical available income above the threshold.

Logic may continue to loop through blocks 434 through 450 until atheoretical adjusted income is determined to not be less than thethreshold amount. Logic may identify products, additional incomesources, or any combination thereof. In some embodiments, a setting oruser selection may be received which determines whether logic identifiesproducts, additional income sources, or both. For example, a request 334may be received which includes an indication that logic should identifyan additional income source but not a product.

In some embodiments, a setting or user selection may be received whichincludes criteria for which products and/or income sources areidentified at respective logic blocks 438 and/or 446. For example, arequest 334 may include an indication of user availability. In anotherexample, a request 334 may include an instruction to only identify asingle additional income source, or a combination of up to a certainnumber of products and/or additional income sources. If a combination ofproducts and/or additional income sources cannot be identified accordingto criteria at respective blocks 438 and/or 446 which will contribute toa theoretical adjusted income not being less than the threshold, logicmay generate an alert, for example, for display via a user interface212. Accordingly, a user interface 212 may receive subsequentinstructions relating to criteria for blocks 438 and/or 446, forexample, via a request 334. Exemplary logic 400A-B may then be restartedconsidering the updated instructions.

If, at block 450, the theoretical adjusted income is determined to notbe less than the threshold, then processing may progress to block 452.At block 452, logic may generate a recommendation message package. Arecommendation message package may comprise one or more aspects ofoutput data 322 and/or a financial estimation 358, as described withrespect to FIG. 3A. For example, a recommendation package may include atleast one recommended product, at least one recommended additionalincome source, or any combination thereof as determined at block 450 tocontribute to a theoretical adjusted income exceeding or being equal toa threshold.

Additionally, or alternatively, a recommendation message package mayinclude information relating to an included product and/or additionalincome source. For example, a recommendation message package may includean effect of a product and/or additional income source on an adjustedavailable income, a theoretical adjusted income, an estimated salary, aschedule requirement, location information, requirements for a productand/or additional income source, contact information helpful for takingadvantage of the product and/or additional income source, or anycombination thereof.

In some embodiments, a recommendation message package may includemultiple recommendations, each comprising one or more products and/oradditional income sources. For example, logic of blocks 432 through 450may be repeated to generate multiple recommendations, each comprisingone or more products and/or additional income sources sufficient tocause a theoretical adjusted income to be greater than or equal to thethreshold.

Processing may progress from block 452 to block 454. At block 454, logicmay provide the recommendation message package for display, for example,via a user interface 212 as described with respect to FIG. 2. Forexample, aspects of a recommendation message package may be displayed asa recommendation 162, 164, and/or 166 as described with respect to FIG.1J. In another example, aspects of a recommendation message package maybe displayed as a recommendation 154, 155, and/or 156 as described withrespect to FIG. 1I. In some embodiments, processing as illustrated inexemplary logic 400B may progress from block 432 to 434 even if anadjusted available income is not less than the threshold. For example, arequest 334 as described in connection with FIG. 3B may include anindication that a number of products and/or additional income sourcesshould be generated without regards to a certain income threshold.Accordingly, products and/or additional income sources may be identifiedin respective blocks 438 and/or block 446 based on a comparison ofproducts and/or income sources. For example, products and/or incomesources may be identified based on having a comparatively higher effecton financial health and/or a theoretical adjusted income, acomparatively higher effect on financial health and/or a theoreticaladjusted income given requirements of the product and/or income source,or other measure. Accordingly, a user may be permitted to accesscontents of a recommendation message package which may affect financialwellbeing without the prerequisite of having an adjusted availableincome less than a threshold. In some embodiments, a product and/orincome source may be identified based on a score of one or more offinancial impact, qualification requirement, schedule requirement,travel requirement, or other factor. Factors may be weighted based on asetting and/or user input.

FIG. 5 illustrates an embodiment of an exemplary computing architecture500 that may be suitable for implementing various embodiments aspreviously described. In various embodiments, the computing architecture500 may comprise or be implemented as part of an electronic device. Insome embodiments, the computing architecture 500 may be representative,for example, of one or more component described herein. In someembodiments, computing architecture 500 may be representative, forexample, of a computing device that implements or utilizes one or moreof a client device 202, a financial analyzer 204, an enterprisedatastore 214, a third-party datastore 216, and/or one or moretechniques described herein. Embodiments are not limited in thiscontext.

As used in this application, the terms “system” and “component” and“module” are intended to refer to a computer-related entity, eitherhardware, a combination of hardware and software, software, or softwarein execution, examples of which are provided by the exemplary computingarchitecture 500. For example, a component can be, but is not limited tobeing, a process running on a processor, a processor, a hard disk drive,multiple storage drives (of optical and/or magnetic storage medium), anobject, an executable, a thread of execution, a program, and/or acomputer. By way of illustration, both an application running on aserver and the server can be a component. One or more components canreside within a process and/or thread of execution, and a component canbe localized on one computer and/or distributed between two or morecomputers. Further, components may be communicatively coupled to eachother by various types of communications media to coordinate operations.The coordination may involve the uni-directional or bi-directionalexchange of information. For instance, the components may communicateinformation in the form of signals communicated over the communicationsmedia. The information can be implemented as signals allocated tovarious signal lines. In such allocations, each message is a signal.Further embodiments, however, may alternatively employ data messages.Such data messages may be sent across various connections. Exemplaryconnections include parallel interfaces, serial interfaces, and businterfaces.

The computing architecture 500 includes various common computingelements, such as one or more processors, multi-core processors,co-processors, memory units, chipsets, controllers, peripherals,interfaces, oscillators, timing devices, video cards, audio cards,multimedia input/output (I/O) components, power supplies, and so forth.The embodiments, however, are not limited to implementation by thecomputing architecture 500.

As shown in FIG. 5, the computing architecture 500 comprises aprocessing unit 504, a system memory 506 and a system bus 508. Theprocessing unit 504 can be any of various commercially availableprocessors, including without limitation an AMD® Athlon®, Duron® andOpteron® processors; ARM® application, embedded and secure processors;IBM® and Motorola® DragonBall® and PowerPC® processors; IBM and Sony®Cell processors; Intel® Celeron®, Core (2) Duo®, Itanium®, Pentium®,Xeon®, and XScale® processors; and similar processors. Dualmicroprocessors, multi-core processors, and other multi-processorarchitectures may also be employed as the processing unit 504.

The system bus 508 provides an interface for system componentsincluding, but not limited to, the system memory 506 to the processingunit 504. The system bus 508 can be any of several types of busstructure that may further interconnect to a memory bus (with or withouta memory controller), a peripheral bus, and a local bus using any of avariety of commercially available bus architectures. Interface adaptersmay connect to the system bus 508 via a slot architecture. Example slotarchitectures may include without limitation Accelerated Graphics Port(AGP), Card Bus, (Extended) Industry Standard Architecture ((E)ISA),Micro Channel Architecture (MCA), NuBus, Peripheral ComponentInterconnect (Extended) (PCI(X)), PCI Express, Personal Computer MemoryCard International Association (PCMCIA), and the like.

The system memory 506 may include various types of computer-readablestorage media in the form of one or more higher speed memory units, suchas read-only memory (ROM), random-access memory (RAM), dynamic RAM(DRAM), Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), staticRAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM),electrically erasable programmable ROM (EEPROM), flash memory (e.g., oneor more flash arrays), polymer memory such as ferroelectric polymermemory, ovonic memory, phase change or ferroelectric memory,silicon-oxide-nitride-oxide-silicon (SONOS) memory, magnetic or opticalcards, an array of devices such as Redundant Array of Independent Disks(RAID) drives, solid state memory devices (e.g., USB memory, solid statedrives (SSD) and any other type of storage media suitable for storinginformation. In the illustrated embodiment shown in FIG. 5, the systemmemory 506 can include non-volatile memory 510 and/or volatile memory512. In some embodiments, system memory 506 may include main memory. Abasic input/output system (BIOS) can be stored in the non-volatilememory 510.

The computer 502 may include various types of computer-readable storagemedia in the form of one or more lower speed memory units, including aninternal (or external) hard disk drive (HDD) 514, a magnetic floppy diskdrive (FDD) 516 to read from or write to a removable magnetic disk 518,and an optical disk drive 520 to read from or write to a removableoptical disk 522 (e.g., a CD-ROM or DVD). The HDD 514, FDD 516 andoptical disk drive 520 can be connected to the system bus 508 by a HDDinterface 524, an FDD interface 526 and an optical drive interface 528,respectively. The HDD interface 524 for external drive implementationscan include at least one or both of Universal Serial Bus (USB) andInstitute of Electrical and Electronics Engineers (IEEE) 694 interfacetechnologies. In various embodiments, these types of memory may not beincluded in main memory or system memory.

The drives and associated computer-readable media provide volatileand/or nonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For example, a number of program modules canbe stored in the drives and memory units 510, 512, including anoperating system 530, one or more application programs 532, otherprogram modules 534, and program data 536. In one embodiment, the one ormore application programs 532, other program modules 534, and programdata 536 can include or implement, for example, the various techniques,applications, and/or components described herein.

A user can enter commands and information into the computer 502 throughone or more wire/wireless input devices, for example, a keyboard 538 anda pointing device, such as a mouse 540. Other input devices may includemicrophones, infra-red (IR) remote controls, radio-frequency (RF) remotecontrols, game pads, stylus pens, card readers, dongles, finger printreaders, gloves, graphics tablets, joysticks, keyboards, retina readers,touch screens (e.g., capacitive, resistive, etc.), trackballs,trackpads, sensors, styluses, and the like. These and other inputdevices are often connected to the processing unit 504 through an inputdevice interface 542 that is coupled to the system bus 508, but can beconnected by other interfaces such as a parallel port, IEEE 994 serialport, a game port, a USB port, an IR interface, and so forth.

A monitor 544 or other type of display device is also connected to thesystem bus 508 via an interface, such as a video adaptor 546. Themonitor 544 may be internal or external to the computer 502. In additionto the monitor 544, a computer typically includes other peripheraloutput devices, such as speakers, printers, and so forth.

The computer 502 may operate in a networked environment using logicalconnections via wire and/or wireless communications to one or moreremote computers, such as a remote computer 548. In various embodiments,one or more migrations may occur via the networked environment. Theremote computer 548 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer502, although, for purposes of brevity, only a memory/storage device 550is illustrated. The logical connections depicted include wire/wirelessconnectivity to a local area network (LAN) 552 and/or larger networks,for example, a wide area network (WAN) 554. Such LAN and WAN networkingenvironments are commonplace in offices and companies, and facilitateenterprise-wide computer networks, such as intranets, all of which mayconnect to a global communications network, for example, the Internet.

When used in a LAN networking environment, the computer 502 is connectedto the LAN 552 through a wire and/or wireless communication networkinterface or adaptor 556. The adaptor 556 can facilitate wire and/orwireless communications to the LAN 552, which may also include awireless access point disposed thereon for communicating with thewireless functionality of the adaptor 556.

When used in a WAN networking environment, the computer 502 can includea modem 558, or is connected to a communications server on the WAN 554,or has other means for establishing communications over the WAN 554,such as by way of the Internet. The modem 558, which can be internal orexternal and a wire and/or wireless device, connects to the system bus508 via the input device interface 542. In a networked environment,program modules depicted relative to the computer 502, or portionsthereof, can be stored in the remote memory/storage device 550. It willbe appreciated that the network connections shown are exemplary andother means of establishing a communications link between the computerscan be used.

The computer 502 is operable to communicate with wire and wirelessdevices or entities using the IEEE 802 family of standards, such aswireless devices operatively disposed in wireless communication (e.g.,IEEE 802.16 over-the-air modulation techniques). This includes at leastWi-Fi (or Wireless Fidelity), WiMax, and Bluetooth™ wirelesstechnologies, among others. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices. Wi-Fi networks use radiotechnologies called IEEE 802.11x (a, b, g, n, etc.) to provide secure,reliable, fast wireless connectivity. A Wi-Fi network can be used toconnect computers to each other, to the Internet, and to wire networks(which use IEEE 802.3-related media and functions).

FIG. 6 illustrates a block diagram of an exemplary communicationsarchitecture 600 suitable for implementing various embodiments aspreviously described, such as virtual machine migration. Thecommunications architecture 600 includes various common communicationselements, such as a transmitter, receiver, transceiver, radio, networkinterface, baseband processor, antenna, amplifiers, filters, powersupplies, and so forth. The embodiments, however, are not limited toimplementation by the communications architecture 600.

As shown in FIG. 6, the communications architecture 600 comprisesincludes one or more clients 602 and servers 604. In some embodimentscommunications architecture may include or implement one or moreportions of components, applications, and/or techniques describedherein. For example, a client device 202 as described in connection toFIG. 2 may operate as a client 602. In another example, a financialanalyzer 204 as described with respect to FIG. 2 may operate on a server604. The clients 602 and the servers 604 are operatively connected toone or more respective client data stores 608 and server data stores 610that can be employed to store information local to the respectiveclients 602 and servers 604, such as cookies and/or associatedcontextual information. In various embodiments, any one of servers 604may implement one or more of logic flows or operations described hereinin conjunction with storage of data received from any one of clients 602on any of server data stores 610. In one or more embodiments, one ormore of client data store(s) 608 or server data store(s) 610 may includememory accessible to one or more portions of components, applications,and/or techniques described herein.

The clients 602 and the servers 604 may communicate information betweeneach other using a communication framework 606. The communicationsframework 606 may implement any well-known communications techniques andprotocols. The communications framework 606 may be implemented as apacket-switched network (e.g., public networks such as the Internet,private networks such as an enterprise intranet, and so forth), acircuit-switched network (e.g., the public switched telephone network),or a combination of a packet-switched network and a circuit-switchednetwork (with suitable gateways and translators).

The communications framework 606 may implement various networkinterfaces arranged to accept, communicate, and connect to acommunications network. A network interface may be regarded as aspecialized form of an input output interface. Network interfaces mayemploy connection protocols including without limitation direct connect,Ethernet (e.g., thick, thin, twisted pair 10/100/1900 Base T, and thelike), token ring, wireless network interfaces, cellular networkinterfaces, IEEE 802.11a-x network interfaces, IEEE 802.16 networkinterfaces, IEEE 802.20 network interfaces, and the like. Further,multiple network interfaces may be used to engage with variouscommunications network types. For example, multiple network interfacesmay be employed to allow for the communication over broadcast,multicast, and unicast networks. Should processing requirements dictatea greater amount speed and capacity, distributed network controllerarchitectures may similarly be employed to pool, load balance, andotherwise increase the communicative bandwidth required by clients 602and the servers 604. A communications network may be any one and thecombination of wired and/or wireless networks including withoutlimitation a direct interconnection, a secured custom connection, aprivate network (e.g., an enterprise intranet), a public network (e.g.,the Internet), a Personal Area Network (PAN), a Local Area Network(LAN), a Metropolitan Area Network (MAN), an Operating Missions as Nodeson the Internet (OMNI), a Wide Area Network (WAN), a wireless network, acellular network, and other communications networks.

Various embodiments may be implemented using hardware elements, softwareelements, or a combination of both. Examples of hardware elements mayinclude processors, microprocessors, circuits, circuit elements (e.g.,transistors, resistors, capacitors, inductors, and so forth), integratedcircuits, application specific integrated circuits (ASIC), programmablelogic devices (PLD), digital signal processors (DSP), field programmablegate array (FPGA), logic gates, registers, semiconductor device, chips,microchips, chip sets, and so forth. Examples of software may includesoftware components, programs, applications, computer programs,application programs, system programs, machine programs, operatingsystem software, middleware, firmware, software modules, routines,subroutines, functions, methods, procedures, software interfaces,application program interfaces (API), instruction sets, computing code,computer code, code segments, computer code segments, words, values,symbols, or any combination thereof. Determining whether an embodimentis implemented using hardware elements and/or software elements may varyin accordance with any number of factors, such as desired computationalrate, power levels, heat tolerances, processing cycle budget, input datarates, output data rates, memory resources, data bus speeds and otherdesign or performance constraints.

One or more aspects of at least one embodiment may be implemented byrepresentative instructions stored on a machine-readable medium whichrepresents various logic within the processor, which when read by amachine causes the machine to fabricate logic to perform the techniquesdescribed herein. Such representations, known as “IP cores” may bestored on a tangible, machine readable medium and supplied to varioususers or manufacturing facilities to load into the fabrication machinesthat actually make the logic or processor. Some embodiments may beimplemented, for example, using a machine-readable medium or articlewhich may store an instruction or a set of instructions that, ifexecuted by a machine, may cause the machine to perform a method and/oroperations in accordance with the embodiments. Such a machine mayinclude, for example, any suitable processing platform, computingplatform, computing device, processing device, computing system,processing system, computer, processor, or the like, and may beimplemented using any suitable combination of hardware and/or software.The machine-readable medium or article may include, for example, anysuitable type of memory unit, memory device, memory article, memorymedium, storage device, storage article, storage medium and/or storageunit, for example, memory, removable or non-removable media, erasable ornon-erasable media, writeable or re-writeable media, digital or analogmedia, hard disk, floppy disk, Compact Disk Read Only Memory (CD-ROM),Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW),optical disk, magnetic media, magneto-optical media, removable memorycards or disks, various types of Digital Versatile Disk (DVD), a tape, acassette, or the like. The instructions may include any suitable type ofcode, such as source code, compiled code, interpreted code, executablecode, static code, dynamic code, encrypted code, and the like,implemented using any suitable high-level, low-level, object-oriented,visual, compiled and/or interpreted programming language.

1. A computing device for a financial institution, comprising: a networkinterface; processing circuitry coupled to the network interface; andmemory coupled to the processing circuitry, the memory comprisinginstructions that when executed by the processing circuitry cause theprocessing circuitry to: receive at the network interface via anauthenticated communication channel, a first information element, thefirst information element comprising indications of actions associatedwith an irregular income stream of a user, determine a supplementalincome based in part on the actions associated with the irregular incomestream, receive a second information element at the network interface,the second information element comprising indications of a primaryincome associated with the user, derive an available income based inpart on the supplemental income and the primary income, generate one ormore financial service offers based in part on the available income, andsend, via the network interface, an indication of the one or morefinancial service offers to a device associated with the user.
 2. Thecomputing device of claim 1, the authenticated communication channel afirst authenticated communication channel, the memory comprisinginstructions that when executed by the processing circuitry cause theprocessing circuitry to: receive at the network interface via a secondauthenticated communication channel, a third information element, thethird information element comprising indications of payments associatedwith the user; determine an amount of outgoing funds based in part onthe payments; and derive the available income based in part on thesupplemental income, the primary income, and the amount of outgoingfunds.
 3. The computing device of claim 2, wherein the paymentsassociated with the user are regular payments, irregular payments, orregular and irregular payments.
 4. The computing device of claim 2,wherein the one or more financial service offers is a pre-qualificationfor a loan offer or a credit counseling service offer.
 5. The computingdevice of claim 1, the memory comprising instructions that when executedby the processing circuitry cause the processing circuitry to send, overa network via the network interface, an application programminginterface (API) request to establish the authenticated communicationchannel with a third party associated with the irregular income stream.6. The computing device of claim 1, wherein the actions associated withthe irregular income stream of the user comprise average completedactions in a time period, completed actions in the time period, oraverage completed actions in the time period and completed actions inthe time period.
 7. The computing device of claim 6, the firstinformation element comprising an indication of a source of thesupplemental income.
 8. The computing device of claim 7, the memorycomprising instructions that when executed by the processing circuitrycause the processing circuitry to determine the supplemental incomebased on the source, the actions, and whether the actions are completedactions or average completed actions, or both average and completedactions.
 9. The computing device of claim 7, wherein the sourcecomprises a ride hailing service, a rental service, a media streamingservice, a content distribution service, a social media service.
 10. Atleast one machine-readable storage medium comprising instructions thatwhen executed by a processor at a computing platform, cause theprocessor to: receive at the network interface via an authenticatedcommunication channel, a first information element, the firstinformation element comprising indications of actions associated with anirregular income stream of a user; determine a supplemental income basedin part on the actions associated with the irregular income stream;receive a second information element at the network interface, thesecond information element comprising indications of a primary incomeassociated with the user; derive an available income based in part onthe supplemental income and the primary income; generate one or morefinancial service offers based in part on the available income; andsend, via the network interface, an indication of the one or morefinancial service offers to a device associated with the user.
 11. Theat least one machine-readable storage medium of claim 1, theauthenticated communication channel a first authenticated communicationchannel, the medium comprising instructions that further cause theprocessor to: receive at the network interface via a secondauthenticated communication channel, a third information element, thethird information element comprising indications of future paymentsassociated with the user; determine an amount of outgoing funds based inpart on the future payments; and derive the available income based inpart on the supplemental income, the primary income, and the amount ofoutgoing funds.
 12. The at least one machine-readable storage medium ofclaim 11, wherein the payments associated with the user are regularpayments, irregular payments, or regular and irregular payments.
 13. Theat least one machine-readable storage medium of claim 11, wherein theone or more financial service offers is a pre-qualification for a loanoffer or a credit counseling service offer.
 14. The at least onemachine-readable storage medium of claim 10, comprising instructionsthat further cause the processor to send, over a network via the networkinterface, an application programming interface (API) request toestablish the authenticated communication channel with a third partyassociated with the irregular income stream.
 15. The at least onemachine-readable storage medium of claim 10, wherein the actionsassociated with the irregular income stream of the user comprise averagecompleted actions in a time period, completed actions in the timeperiod, or average completed actions in the time period and completedactions in the time period.
 16. The at least one machine-readablestorage medium of claim 15, the first information element comprising anindication of a source of the supplemental income.
 17. The at least onemachine-readable storage medium of claim 16, comprising instructionsthat further cause the processor to determine the supplemental incomebased on the source, the actions, and whether the actions are completedactions or average completed actions, or both average and completedactions.
 18. The at least one machine-readable storage medium of claim16, wherein the source comprises a ride hailing service, a rentalservice, a media streaming service, a content distribution service, asocial media service.
 19. A computer implemented method, comprising:receiving at a network interface via an authenticated communicationchannel, a first information element, the first information elementcomprising indications of actions associated with an irregular incomestream of a user; determining a supplemental income based in part on theactions associated with the irregular income stream; receiving a secondinformation element at the network interface, the second informationelement comprising indications of a primary income associated with theuser; deriving an available income based in part on the supplementalincome and the primary income; generating one or more financial serviceoffers based in part on the available income; and sending, via thenetwork interface, an indication of the one or more financial serviceoffers to a device associated with the user.
 20. The computerimplemented method of claim 19, the authenticated communication channela first authenticated communication channel, the method comprising:receiving at the network interface via a second authenticatedcommunication channel, a third information element, the thirdinformation element comprising indications of future payments associatedwith the user; determining an amount of outgoing funds based in part onthe future payments; and deriving the available income based in part onthe supplemental income, the primary income, and the amount of outgoingfunds.